Just for the reference. This has been discussed as a part of other email thread discussed here: http://lkml.kernel.org/r/20151027122647.GG9891%40dhcp22.suse.cz I am _really_ sorry for hijacking that one - I didn't intend to do so but my remark ended up in a full discussion. If I knew it would go that way I wouldn't even mention it. On Fri 28-08-15 11:25:30, Tejun Heo wrote: > On the default hierarchy, all memory consumption will be accounted > together and controlled by the same set of limits. Always enable > kmemcg on the default hierarchy. > > Signed-off-by: Tejun Heo <tj@xxxxxxxxxx> > --- > mm/memcontrol.c | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/mm/memcontrol.c b/mm/memcontrol.c > index c94b686..8a5dd01 100644 > --- a/mm/memcontrol.c > +++ b/mm/memcontrol.c > @@ -4362,6 +4362,13 @@ mem_cgroup_css_online(struct cgroup_subsys_state *css) > if (ret) > return ret; > > + /* kmem is always accounted together on the default hierarchy */ > + if (cgroup_on_dfl(css->cgroup)) { > + ret = memcg_activate_kmem(memcg, PAGE_COUNTER_MAX); > + if (ret) > + return ret; > + } > + > /* > * Make sure the memcg is initialized: mem_cgroup_iter() > * orders reading memcg->initialized against its callers > -- > 2.4.3 -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
