From: David Rientjes <rientjes@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Oleg Nesterov <oleg@redhat.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-mm@kvack.org
Subject: [patch -mm 5/6] oom: sacrifice child with highest badness score for parent fix
Date: Tue, 8 Jun 2010 20:59:24 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1006082058260.6219@chino.kir.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1006082053130.6219@chino.kir.corp.google.com>
Elaborate on the comment in oom_kill_process() so it's clear why a
killable child with a different mm is sacrificied for its parent.
At the same time, rename auto variable `c' to "child" and move "cpoints"
inside the list_for_each_entry() loop with a more descriptive name as
akpm suggests.
Signed-off-by: David Rientjes <rientjes@google.com>
---
mm/oom_kill.c | 25 +++++++++++++++----------
1 files changed, 15 insertions(+), 10 deletions(-)
diff --git a/mm/oom_kill.c b/mm/oom_kill.c
--- a/mm/oom_kill.c
+++ b/mm/oom_kill.c
@@ -440,7 +440,7 @@ static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order,
const char *message)
{
struct task_struct *victim = p;
- struct task_struct *c;
+ struct task_struct *child;
struct task_struct *t = p;
unsigned long victim_points = 0;
struct timespec uptime;
@@ -462,22 +462,27 @@ static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order,
message, task_pid_nr(p), p->comm, points);
task_unlock(p);
- /* Try to sacrifice the worst child first */
+ /*
+ * If any of p's children has a different mm and is eligible for kill,
+ * the one with the highest badness() score is sacrificed for its
+ * parent. This attempts to lose the minimal amount of work done while
+ * still freeing memory.
+ */
do_posix_clock_monotonic_gettime(&uptime);
do {
- unsigned long cpoints;
+ list_for_each_entry(child, &t->children, sibling) {
+ unsigned long child_points;
- list_for_each_entry(c, &t->children, sibling) {
- if (c->mm == p->mm)
+ if (child->mm == p->mm)
continue;
- if (mem && !task_in_mem_cgroup(c, mem))
+ if (mem && !task_in_mem_cgroup(child, mem))
continue;
/* badness() returns 0 if the thread is unkillable */
- cpoints = badness(c, uptime.tv_sec);
- if (cpoints > victim_points) {
- victim = c;
- victim_points = cpoints;
+ child_points = badness(child, uptime.tv_sec);
+ if (child_points > victim_points) {
+ victim = child;
+ victim_points = child_points;
}
}
} while_each_thread(p, t);
--
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 prev parent reply other threads:[~2010-06-09 3:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 3:59 [patch -mm 0/6] oom: various tiny cleanups and fixes David Rientjes
2010-06-09 3:59 ` [patch -mm 1/6] oom: dump_tasks use find_lock_task_mm too fix David Rientjes
2010-06-09 3:59 ` [patch -mm 2/6] oom: protect dereferencing of task's comm David Rientjes
2010-06-09 3:59 ` [patch -mm 3/6] oom: add has_intersects_mems_allowed UMA variant David Rientjes
2010-06-09 3:59 ` [patch -mm 4/6] oom: introduce find_lock_task_mm to fix mm false positives fix David Rientjes
2010-06-09 3:59 ` David Rientjes [this message]
2010-06-09 3:59 ` [patch -mm 6/6] oom: improve commentary in dump_tasks() David Rientjes
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=alpine.DEB.2.00.1006082058260.6219@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=oleg@redhat.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