lkml.org 
[lkml]   [2011]   [Feb]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: KSM kernel interface
Date
Thanks for the patch. I will try it out later today.

>
> > Perhaps there is a small kernel modification that might make this
> possible
> > or provide a sysfs flag that enables it (off by default of course)?
>
> Indeed it could be added if there were a general call for it; but ksmd
> would tend to get wasteful, and the only call for it that I remember is
> for testing.
>
> I expect you've noticed the transparent_hugepage/enabled "always" option,
> and you are thinking something like that could be done for KSM: yes.
>
>

For what its worth, I believe that the option in sysfs to enable KSM
globally would be useful to have. I'm sure i'm not the only one. Its not
like it would be a great deal of overhead, since the KSM machinery is
already there anyway, just needs a flag to enable it at runtime instead
of at boot.

I have at least one system running mostly legacy code that is according
to ESXI's memory report, using only 400mb per gigabyte thanks to
transparent page sharing. I would very much like to be able to have that
level of memory saving on arbitrary code running on bare metal.
Administrators can make their own judgement about ksmd's CPU usage, and
the defaults already suit most people. I don't really see how having
that extra flag (defaulting to off of course) would hurt.

Thanks



\
 
 \ /
  Last update: 2011-02-20 03:49    [from the cache]
©2003-2011 Jasper Spaans