From: Roman Gushchin <guro@fb.com>
To: linux-mm@kvack.org
Cc: Roman Gushchin <guro@fb.com>
Subject: [v3 0/6] cgroup-aware OOM killer
Date: Wed, 21 Jun 2017 22:19:10 +0100 [thread overview]
Message-ID: <1498079956-24467-1-git-send-email-guro@fb.com> (raw)
This patchset makes the OOM killer cgroup-aware.
Patch 1 causes out_of_memory() look at the oom_victim counter
to decide if a new victim is required.
Patch 2 is main patch which implements cgroup-aware OOM killer.
Patch 3 adds some debug output, which can be refined later.
Patch 4 introduces per-cgroup oom_score_adj knob.
Patch 5 fixes a problem with too many processes receiving an
access to the memory reserves.
Patch 6 is docs update.
v1:
https://lkml.org/lkml/2017/5/18/969
v2:
- Reworked victim selection based on feedback
from Michal Hocko, Vladimir Davydov and Johannes Weiner
- "Kill all tasks" is now an opt-in option, by default
only one process will be killed
- Added per-cgroup oom_score_adj
- Refined oom score calculations, suggested by Vladimir Davydov
- Converted to a patchset
v3:
- Fixed swap accounting
- Switched to use oom_victims counter to prevent unnecessary kills
- TIF_MEMDIE is set only when necessary
- Moved all oom victim killing code into oom_kill.c
- Merged commits 1-4 into 6
- Separated oom_score_adj logic into a separate commit 4
- Separated debug output into a separate commit 3
Roman Gushchin (6):
mm, oom: use oom_victims counter to synchronize oom victim selection
mm, oom: cgroup-aware OOM killer
mm, oom: cgroup-aware OOM killer debug info
mm, oom: introduce oom_score_adj for memory cgroups
mm, oom: don't mark all oom victims tasks with TIF_MEMDIE
mm,oom,docs: describe the cgroup-aware OOM killer
Documentation/cgroup-v2.txt | 44 ++++++++++
include/linux/memcontrol.h | 23 +++++
include/linux/oom.h | 3 +
kernel/exit.c | 2 +-
mm/memcontrol.c | 209 ++++++++++++++++++++++++++++++++++++++++++++
mm/oom_kill.c | 202 ++++++++++++++++++++++++++++--------------
6 files changed, 416 insertions(+), 67 deletions(-)
--
2.7.4
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2017-06-21 21:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 21:19 Roman Gushchin [this message]
2017-06-21 21:19 ` [v3 1/6] mm, oom: use oom_victims counter to synchronize oom victim selection Roman Gushchin
[not found] ` <201706220040.v5M0eSnK074332@www262.sakura.ne.jp>
2017-06-22 16:58 ` Roman Gushchin
2017-06-22 20:37 ` Tetsuo Handa
[not found] ` <201706230537.IDB21366.SQHJVFOOFOMFLt-JPay3/Yim36HaxMnTkn67Xf5DAMn2ifp@public.gmane.org>
2017-06-22 21:52 ` Tetsuo Handa
2017-06-29 18:47 ` Roman Gushchin
2017-06-29 20:13 ` Tetsuo Handa
2017-06-29 9:04 ` Michal Hocko
2017-06-21 21:19 ` [v3 2/6] mm, oom: cgroup-aware OOM killer Roman Gushchin
2017-07-10 23:05 ` David Rientjes
2017-07-11 12:51 ` Roman Gushchin
2017-07-11 20:56 ` David Rientjes
2017-07-12 12:11 ` Roman Gushchin
2017-07-12 20:26 ` David Rientjes
2017-06-21 21:19 ` [v3 3/6] mm, oom: cgroup-aware OOM killer debug info Roman Gushchin
2017-06-21 21:19 ` [v3 4/6] mm, oom: introduce oom_score_adj for memory cgroups Roman Gushchin
2017-06-21 21:19 ` [v3 5/6] mm, oom: don't mark all oom victims tasks with TIF_MEMDIE Roman Gushchin
2017-06-29 8:53 ` Michal Hocko
2017-06-29 18:45 ` Roman Gushchin
2017-06-30 8:25 ` Michal Hocko
2017-06-21 21:19 ` [v3 6/6] mm,oom,docs: describe the cgroup-aware OOM killer Roman Gushchin
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=1498079956-24467-1-git-send-email-guro@fb.com \
--to=guro@fb.com \
--cc=linux-mm@kvack.org \
/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;
as well as URLs for NNTP newsgroup(s).