[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1709111345320.102819@chino.kir.corp.google.com>
Date: Mon, 11 Sep 2017 13:48:39 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Roman Gushchin <guro@...com>
cc: linux-mm@...ck.org, Michal Hocko <mhocko@...nel.org>,
Vladimir Davydov <vdavydov.dev@...il.com>,
Johannes Weiner <hannes@...xchg.org>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
Andrew Morton <akpm@...ux-foundation.org>,
Tejun Heo <tj@...nel.org>, kernel-team@...com,
cgroups@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [v8 3/4] mm, oom: add cgroup v2 mount option for cgroup-aware
OOM killer
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.
Powered by blists - more mailing lists