[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1801251552320.161808@chino.kir.corp.google.com>
Date: Thu, 25 Jan 2018 15:53:41 -0800 (PST)
From: David Rientjes <rientjes@...gle.com>
To: Andrew Morton <akpm@...ux-foundation.org>,
Roman Gushchin <guro@...com>
cc: Michal Hocko <mhocko@...nel.org>,
Vladimir Davydov <vdavydov.dev@...il.com>,
Johannes Weiner <hannes@...xchg.org>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
Tejun Heo <tj@...nel.org>, kernel-team@...com,
cgroups@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: [patch -mm v2 0/3] mm, memcg: introduce oom policies
There are three significant concerns about the cgroup aware oom killer as
it is implemented in -mm:
(1) allows users to evade the oom killer by creating subcontainers or
using other controllers since scoring is done per cgroup and not
hierarchically,
(2) does not allow the user to influence the decisionmaking, such that
important subtrees cannot be preferred or biased, and
(3) unfairly compares the root mem cgroup using completely different
criteria than leaf mem cgroups and allows wildly inaccurate results
if oom_score_adj is used.
This patchset aims to fix (1) completely and, by doing so, introduces a
completely extensible user interface that can be expanded in the future.
It eliminates the mount option for the cgroup aware oom killer entirely
since it is now enabled through the root mem cgroup's oom policy.
It preserves memory.oom_group behavior.
---
Applied on top of -mm.
Documentation/cgroup-v2.txt | 64 ++++++++++++++++++++++++++++-----------------
include/linux/cgroup-defs.h | 5 ----
include/linux/memcontrol.h | 21 +++++++++++++++
kernel/cgroup/cgroup.c | 13 +--------
mm/memcontrol.c | 64 ++++++++++++++++++++++++++++++++++++---------
5 files changed, 114 insertions(+), 53 deletions(-)
Powered by blists - more mailing lists