On Thu, 23 Mar 2000, Stuart Hughes wrote:
> Download version 1.2 from http://www.rtai.org/ and look in the lxrt
> sub-directory. Basically, RTAI has its own set of syscalls, to move a
> process into the hard realtime mode, it make a syscall that sets the
> process in a state whereby linux no longer schedules it, and RTAI takes
> over scheduling responsibility. To use this mode, a user has to lock
> his pages into memory with mlock. You are correct that RTAI system does
> switch the mmu context.
What happens if a process in hard real time mode makes a system call (like
write to a file or send a packet), and the kernel has just been preempted
from a system call of some normal process? Does the control return to the
preempted kernel until normal syscall is done and then syscall done from RT
continues? This would be the easiest way to solve this conflict.
--
Tomek
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
