Messages in this thread | | | Subject | Re: [PATCH 2/2] mm, memcg: Optionally disable memcg by default using Kconfig | From | Davidlohr Bueso <> | Date | Wed, 20 May 2015 06:47:46 -0700 |
| |
On Wed, 2015-05-20 at 13:50 +0100, Mel Gorman wrote: > +config MEMCG_DEFAULT_ENABLED > + bool "Automatically enable memory resource controller" > + default y > + depends on MEMCG > + help > + The memory controller has some overhead even if idle as resource > + usage must be tracked in case a group is created and a process > + migrated. As users may not be aware of this and the cgroup_disable= > + option, this config option controls whether it is enabled by > + default. It is assumed that someone that requires the controller > + can find the cgroup_enable= switch. > + > + Say N if unsure. This is default Y to preserve oldconfig and > + historical behaviour.
Out of curiosity, how do you expect distros to handle this? I mean, this is a pretty general functionality and customers won't want to be changing kernels (they may or may not use memcg). iow, will this ever be disabled?
Thanks, Davidlohr
| |