> A problem is "hard realtime" if time constraints are involved in the
> specification of the problem such that, when the time constraint is
> not met, the behaviour of the program is seen as _not correct_.
...
> Note the last two words. The definition doesn't deal with possible
> consequences from wrong behaviour, it just states that the behaviour
This distinction is not useful then, since the success of a hard
real-time process may be far less important than the on-time behavior
of a soft real-time process.
It is only the consequences that matter, and the OS can not determine
how expensive the consequences are. Humans let the OS know, and the
OS must avoid missing deadlines.
(so it was bad to bother Richard Gooch with such a pointless question)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/