Just because an OS is fast enough to deal with the problem at hand
does not mean that you can guarantee that this will always be
repeatable. You just don't get any guarantees of the upper limit
of time that something will take.
Dick Johnson wrote:
>`Realtime` basically means that if you can handle all external events
>in a timely manner it's realtime. If the response to an external event
>is delayed so that it is no longer current, it is not realtime. If
>external events are lost, it's broken -period. Such words as "current"
>and "timely" are application-specific. Therefore, if you are measuring
>the wear-out of some gears, a program written in interpreted BASIC on a
>CP/M machine is "realtime". However, if you are trying to make images
>from data acquired at 30 megabytes/second, you need many parallel
>DSPs, tightly-coupled, to achieve "realtime".
Mike T. Miller
mtm@csoft.net
-
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/