On 6/9/06, Yang Huang <justin8086@xxxxxxxxx> wrote:
Hi list,
I am trying to figure out why Linux is not a real time OS, which i
believe is true but want to know which part of the OS introduces
nondeterministics.
I try to start with the implementation of spin_lock family, but it
seems that interrupt has been disabled and nothing can interfare. also
the interrupt service routine is said to suffer from delays, but as a
newbie I feel no place to start with.
Any hints, links or ideas that can shed some light on this issue will
be highly appreciated.
with kind regards,
Yang
The Linux user processes scheduler provides the POSIX 1003.13 standard of real-time
extension. The POSIX standard defines a "Multi-User Real-Time System Profile" which
ensures that "Real-time" processes are always executed in a predictable order. Although
Linux meets this standard the resultant task cannot be defined as real-time task, since
kernel activity can block it.
extension. The POSIX standard defines a "Multi-User Real-Time System Profile" which
ensures that "Real-time" processes are always executed in a predictable order. Although
Linux meets this standard the resultant task cannot be defined as real-time task, since
kernel activity can block it.
Try to add endless while loop in system calls ...
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
