On Mon, 27 Aug 2007, Carsten Emde wrote: > I don't know what exactly "soft real-time" is, and I don't think there is an > exact definition of it. The term "hard real-time", however, is well defined. > It is the same as "real-time". It means that a system never ever exceeds a > previously defined maximum latency.
As long as your non-realtime tasks are allowed to take locks, that also prevent real-time tasks from preempting them, and as long as you haven't proved that all those locks in all your non-realtime sources can never under any circumstances last longer than your pre-defined limit, it is not a hard-realtime OS. This doesn't mean I don't like rt-opreempt:-) One just has to understand clearly its features and limitations. Thanks Guennadi --------------------------------- Guennadi Liakhovetski, Ph.D. DSA Daten- und Systemtechnik GmbH Pascalstr. 28 D-52076 Aachen Germany - To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
