On Fri 28-08-15 13:41:40, Tejun Heo wrote: > On Fri, Aug 28, 2015 at 07:14:38PM +0200, Michal Hocko wrote: > > On Fri 28-08-15 19:49:18, Vladimir Davydov wrote: > > > On Fri, Aug 28, 2015 at 11:25:30AM -0400, 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. > > > > > > IMO we should introduce a boot time knob for disabling it, because kmem > > > accounting is still not perfect, besides some users might prefer to go > > > w/o it for performance reasons. > > > > I would even argue for opt-in rather than opt-out. > > Definitely not. The runtime overhead is not negligible and I do not see why everybody should be paying that price by default. I can definitely see the reason why somebody would want to enable the kmem accounting but many users will probably never care because the kernel footprint would be in the noise wrt. user memory. > We wanna put all memory consumptions under the same roof by default. But I am not sure we will ever achieve this. E.g. hugetlb memory is way too different to be under the same charging by default IMO. Also all the random drivers calling into the page allocator directly in the user context would need to charge explicitly. -- 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
