Messages in this thread | | | Subject | Re: [PATCH] [request for inclusion] Realtime LSM | From | "Jack O'Quin" <> | Date | Fri, 07 Jan 2005 14:27:26 -0600 |
| |
Matt Mackall <mpm@selenic.com> writes:
> On Thu, Jan 06, 2005 at 11:54:05PM -0600, Jack O'Quin wrote: >> 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.
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |