On Mon, Sep 4, 2017 at 7:21 AM, Roman Gushchin <guro@xxxxxx> wrote: > Introducing of cgroup-aware OOM killer changes the victim selection > algorithm used by default: instead of picking the largest process, > it will pick the largest memcg and then the largest process inside. > > This affects only cgroup v2 users. > > To provide a way to use cgroups v2 if the old OOM victim selection > algorithm is preferred for some reason, the nogroupoom mount option > is added. Is this mount option or boot parameter? From the code, it seems like a boot parameter. -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
