From: Yafang Shao <laoar.shao@gmail.com>
To: akpm@linux-foundation.org
Cc: shakeelb@google.com, hannes@cmpxchg.org, mhocko@kernel.org,
guro@fb.com, gthelen@google.com, linux-mm@kvack.org,
Yafang Shao <laoar.shao@gmail.com>
Subject: [PATCH 2/2] mm, memcg: don't try to kill a process if memcg is not populated
Date: Sat, 2 May 2020 10:34:52 -0400 [thread overview]
Message-ID: <20200502143452.7640-3-laoar.shao@gmail.com> (raw)
In-Reply-To: <20200502143452.7640-1-laoar.shao@gmail.com>
Recently Shakeel reported a issue which also confused me serveral months
earlier. Bellow is his report -
Lowering memory.max can trigger an oom-kill if the reclaim does not
succeed. However if oom-killer does not find a process for killing, it
dumps a lot of warnings.
Deleting a memcg does not reclaim memory from it and the memory can
linger till there is a memory pressure. One normal way to proactively
reclaim such memory is to set memory.max to 0 just before deleting the
memcg. However if some of the memcg's memory is pinned by others, this
operation can trigger an oom-kill without any process and thus can log a
lot un-needed warnings. So, ignore all such warnings from memory.max.
[shakeelb@google.com: commit log above]
A better way to avoid this issue is to avoid trying to kill a process if
memcg is not populated.
Note that OOM is different with OOM kill. OOM is a status that the
system or memcg is out of memory, while OOM kill is a result that a
process inside this memcg is killed when this memcg is in OOM status.
That is the same reason why there're both MEMCG_OOM event and
MEMCG_OOM_KILL event. If we have already known that there's nothing to
kill, i.e. the memcg is not populated, then we don't need to have a try.
Cc: Shakeel Butt <shakeelb@google.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: Michal Hocko <mhocko@kernel.org>
Cc: Roman Gushchin <guro@fb.com>
Cc: Greg Thelen <gthelen@google.com>
Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
---
mm/memcontrol.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 985edce98491..29afe3df9d98 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -6102,6 +6102,10 @@ static ssize_t memory_max_write(struct kernfs_open_file *of,
}
memcg_memory_event(memcg, MEMCG_OOM);
+
+ if (!cgroup_is_populated(memcg->css.cgroup))
+ break;
+
if (!mem_cgroup_oom_kill(memcg, GFP_KERNEL, 0))
break;
}
--
2.18.2
next prev parent reply other threads:[~2020-05-02 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 14:34 [PATCH 0/2] memcg oom: don't try to kill a process if there is no process Yafang Shao
2020-05-02 14:34 ` [PATCH 1/2] mm, memcg: better name mem_cgroup_out_of_memory() Yafang Shao
2020-05-03 22:20 ` Shakeel Butt
2020-05-02 14:34 ` Yafang Shao [this message]
2020-05-03 22:59 ` [PATCH 2/2] mm, memcg: don't try to kill a process if memcg is not populated Shakeel Butt
2020-05-04 3:03 ` Yafang Shao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200502143452.7640-3-laoar.shao@gmail.com \
--to=laoar.shao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gthelen@google.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=shakeelb@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox