7 Jan
2005
7 Jan
'05
4:21 p.m.
* Matt Mackall (mpm(a)selenic.com) wrote:
On Thu, Jan 06, 2005 at 11:54:05PM -0600, Jack
O'Quin wrote:
It can actually be done with plain ol' rlimits (RLIMIT_MEMLOCK).
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. The trouble with introducing something into the kernel
is that once
done, it can't be undone. So you're absolutely going to meet
resistance to anything that can be a) done sufficiently in userspace
or b) can reasonably be done in a more generic manner so as to meet
the needs of a wider future audience. The onus is on the submitter to
meet these requirements because we can't easily kick out a broken API
after we accept it.
Indeed (although in this case it's not adding an API as much as using an
existing one).
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net