Locking kdecore into memory
neundorf at kde.org
Wed Jan 24 20:50:46 GMT 2007
On Tuesday 23 January 2007 18:03, Lubos Lunak wrote:
> On Monday 22 January 2007 08:31, subbukk wrote:
> > On Monday 22 January 2007 05:31, Stefan Teleman wrote:
> > > On Sunday 21 January 2007 17:25, Richard Moore wrote:
> > > > 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.
> > >
> > > A lot. :-)
> > True. Pinning all of kdecore into RAM is an overkill as many of its pages
> > may be used rarely or not at all.
> Not all of it, just what's used. I think mlockall( MCL_CURRENT ) at a
> suitable place should do. Besides, 30M is hardly a lot with today's
> machines, I'd gladly give it if I knew I'll never ever see this 1G machine
> dead for minutes or rather even tens of them.
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.
Work: alexander.neundorf AT jenoptik.com - http://www.jenoptik-los.de
Home: neundorf AT kde.org - http://www.kde.org
alex AT neundorf.net - http://www.neundorf.net
More information about the kde-core-devel