I thought that the memory locking was done by a seperate system call, and that setting the scheduling policy to SCHED_FIFO or SCHED_RR by itself did not lock memory. Also, you can still allocate memory after making this call. I had assumed that if you use memlockall (or however it's spelled), that any memory allocated after the call will also be locked (is this correct?)
yes it is independant from the scheduling policy ... the memory locking _could_, as yves proposed, be used independantly from the realtime scheduling...
cheers... tim