On Mon, 11 Sep 2017, 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 can't imagine that Tejun would be happy with a new mount option, especially when it's not required. OOM behavior does not need to be defined at mount time and for the entire hierarchy. It's possible to very easily implement a tunable as part of mem cgroup that is propagated to descendants and controls the oom scoring behavior for that hierarchy. It does not need to be system wide and affect scoring of all processes based on which mem cgroup they are attached to at any given time. -- 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
