On Thu, 4 Mar 1999, Mike Cravens wrote:
> Would anyone care to comment on the difference between "hard real-time"
> and "soft real-time"?
>
> Mike Cravens
>
"Soft" means it would be nice if the schedule was met most of
the time, but an occasional miss can be tolerated (this is what NT
delivers for its "real-time" priority). It is useful for most "user
interface" types of problems. For example, streaming video, if a few
frames are missed in this application, the picture may not be completely
pleasing to the user, but no real harm is done.
"Hard" means that the correct operation of the system depends not only on
the correctness of the algorithm processed but also on the time in which
it completes; missed deadlines mean total catastrophic failure of the
system. An example would be an industrial robot on a manufacturing
line, or perhaps a "smart" weapon, or some other physical system with
real physical consequences (in the cases mentioned here that could be
serious injury or death, which is either definitely not the objective or
positively the objective of the system).
-Don
--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
----
For more information on Real-Time Linux see:
http://www.rtlinux.org/~rtlinux/
