Locking kdecore into memory

Richard Moore richmoore44 at gmail.com
Sun Jan 21 22:25:30 GMT 2007

On 1/21/07, Lubos Lunak <l.lunak at suse.cz> wrote:

So we have some sort of kdeinit like process that runs setuid and
calls mlockall()? That would be able to lock the libraries into ram I
guess. To be useful though, how much would we have to lock? kdecore,
kdelibs, qt, X11 and libc I guess. That's quite a bit. We'd also need
to consider if this would make the X server (and other processes like
our apps) to be swapped out which would cause general performance to
go down. If the X server is swapped out then

> > You
> > can also get bitten by the fact that if two processes lock a page, and
> > one unlocks it the page gets unlocked - there is no ref count.
>  I don't think there'd be any unlocking.

That means we need to do this on a system wide basis, otherwise you
wouldn't be able to run multiple sessions. I guess it could be argued
though that there's still a net win as the behaviour would merely
return to what we have now.



More information about the kde-core-devel mailing list