From: Niv Yehezkel <executerx@gmail.com>
To: linux-mm@kvack.org, akpm@linux-foundation.org,
rientjes@google.com, mhocko@suse.cz, hannes@cmpxchg.org,
oleg@redhat.com
Subject: [PATCH] oom: break after selecting process to kill
Date: Thu, 11 Sep 2014 17:33:39 -0400 [thread overview]
Message-ID: <20140911213338.GA4098@localhost.localdomain> (raw)
There is no need to fallback and continue computing
badness for each running process after we have found a
process currently performing the swapoff syscall. We ought to
immediately select this process for killing.
Signed-off-by: Niv Yehezkel <executerx@gmail.com>
---
mm/oom_kill.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/mm/oom_kill.c b/mm/oom_kill.c
index 1e11df8..68ac30e 100644
--- a/mm/oom_kill.c
+++ b/mm/oom_kill.c
@@ -305,6 +305,7 @@ static struct task_struct *select_bad_process(unsigned int *ppoints,
struct task_struct *g, *p;
struct task_struct *chosen = NULL;
unsigned long chosen_points = 0;
+ bool process_selected = false;
rcu_read_lock();
for_each_process_thread(g, p) {
@@ -315,7 +316,8 @@ static struct task_struct *select_bad_process(unsigned int *ppoints,
case OOM_SCAN_SELECT:
chosen = p;
chosen_points = ULONG_MAX;
- /* fall through */
+ process_selected = true;
+ break;
case OOM_SCAN_CONTINUE:
continue;
case OOM_SCAN_ABORT:
@@ -324,6 +326,8 @@ static struct task_struct *select_bad_process(unsigned int *ppoints,
case OOM_SCAN_OK:
break;
};
+ if (process_selected)
+ break;
points = oom_badness(p, NULL, nodemask, totalpages);
if (!points || points < chosen_points)
continue;
--
1.7.10.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:[~2014-09-11 21:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 21:33 Niv Yehezkel [this message]
2014-09-12 1:22 ` [PATCH] oom: break after selecting process to kill Zhang Zhen
2014-09-12 7:39 ` Niv Yehezkel
2014-09-12 8:08 ` Michal Hocko
2014-09-12 8:23 ` Niv Yehezkel
2014-09-12 12:18 ` Michal Hocko
2014-09-12 12:21 ` Niv Yehezkel
2014-09-12 12:31 ` Michal Hocko
2014-09-14 20:46 ` David Rientjes
2014-09-23 18:30 ` Michal Hocko
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=20140911213338.GA4098@localhost.localdomain \
--to=executerx@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=oleg@redhat.com \
--cc=rientjes@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;
as well as URLs for NNTP newsgroup(s).