On Tue 03-10-17 13:49:36, Roman Gushchin wrote: > On Tue, Oct 03, 2017 at 01:50:36PM +0200, Michal Hocko wrote: > > On Wed 27-09-17 14:09:35, Roman Gushchin wrote: > > > Add a "groupoom" cgroup v2 mount option to enable the cgroup-aware > > > OOM killer. If not set, the OOM selection is performed in > > > a "traditional" per-process way. > > > > > > The behavior can be changed dynamically by remounting the cgroupfs. > > > > I do not have a strong preference about this. I would just be worried > > that it is usually systemd which tries to own the whole hierarchy > > I actually like this fact. > > It gives us the opportunity to change the default behavior for most users > at the point when we'll be sure that new behavior is better; but at the same > time we'll save full compatibility on the kernel level. Well, I would be much more skeptical because I simply believe that neither of the approach is better in general. It really depends on the usecases. And systemd or whoever mounts the hierarchy has no slightest idea what is the case. So we might end up with a global knob to control the mount point after all. But as I've said no strong opinion on that. -- 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
