> Improving the average latency of systems is a worthy goal, and there's
> no denying that 'sorta realtime' has its place, however it's no substitute
> for the real thing. A soft realtime system screws up only on occasion,
> but - bugs excepted - a hard realtime system *never* does.
Engineering assumption. Your hardware and/or software always contains
at least one bug. Therefore even in hard real time you must design
and code for the failure case. Hard real time is just doing
everything humanly possible to meet it's deadlines.
The difference with soft real time, is that something that is humanly
possible to do was left off.
Despite the strong relationship to mathematics there are no absolutes
in computer science. Especially hard real time.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/