7 Jan
2005
7 Jan
'05
4:26 p.m.
Matt Mackall <mpm(a)selenic.com> writes:
On Thu, Jan 06, 2005 at 11:54:05PM -0600, Jack
O'Quin wrote:
If you're "pretty sure", please explain how locking a shared memory
segment prevents the code and stack of the client's realtime thread
from page faulting.
--
joq
Note that sched_setschedule() provides no way to
handle the mlock()
requirement, which cannot be done from another process.
I'm pretty sure that part can be done by a privileged server handing
out mlocked shared memory segments.