Locking kdecore into memory
thiago at kde.org
Wed Jan 24 21:25:44 GMT 2007
Alexander Neundorf wrote:
>Should this be done always, i.e. also when running a KDE app under
>I'm not sure this will make a good impression "I just run one single KDE
> app and it mlocks() 30 MB of RAM !"
>Also what happens if other desktop environments then also consider it a
> good idea and Gnome starts locking memory, maybe Mozilla too and of
> course OOo too, then it will somehow suck.
Since mlocking this amount of memory will require root privileges, this
can only work on a full KDE session, in which we can run a setuid root
process to do the operation.
This means we won't have the issue if other desktops start doing it and
you just happen to run one app from it.
But it will be a problem if you have more than one desktop running on the
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the kde-core-devel