::Along the same lines (matt probably knows the answer) is it
::easy to force paging in and locking down of any memory associated
::with a process so that mlockall(MCL_FUTURE) together with
::an appropriate memorylocked limit gives the requested
::memory semantics? I'd have to check through the
Hmm. Well, mlock() is one of those system calls that virtually
nobody has worked on since inception. The most I've done with it
has been to fix bugs. The resource issues for mlock() aren't
really good enough to prevent misuse in a general multiuser system.
The resource is pe
Why is the mlock(2) call restricted to the super user instead
of enforcing it through per-user or per-login class limits?
I was checking to see if most of the pieces were in place for
"mlockall(MCL_FUTURE)" and noticed the "memorylocked infinity"
setting in limits (I didn't know about memorylocked
3 matches
Mail list logo
