From: Niv Yehezkel <executerx@gmail.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
rientjes@google.com, hannes@cmpxchg.org, oleg@redhat.com
Subject: Re: [PATCH] oom: break after selecting process to kill
Date: Fri, 12 Sep 2014 08:21:43 -0400 [thread overview]
Message-ID: <20140912122143.GA20622@localhost.localdomain> (raw)
In-Reply-To: <20140912121817.GE12156@dhcp22.suse.cz>
On Fri, Sep 12, 2014 at 02:18:17PM +0200, Michal Hocko wrote:
> On Fri 12-09-14 04:23:29, Niv Yehezkel wrote:
> [...]
> > From 1e92f232e9367565d93629b54117b27b9bbfebda Mon Sep 17 00:00:00 2001
> > From: Niv Yehezkel <executerx@gmail.com>
> > Date: Fri, 12 Sep 2014 04:21:48 -0400
> > Subject: [PATCH] break after selecting process to kill
> >
> >
>
> Now the justification please ;)
>
> > Signed-off-by: Niv Yehezkel <executerx@gmail.com>
> > ---
> > mm/oom_kill.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> > index 1e11df8..3203578 100644
> > --- a/mm/oom_kill.c
> > +++ b/mm/oom_kill.c
> > @@ -315,7 +315,7 @@ static struct task_struct *select_bad_process(unsigned int *ppoints,
> > case OOM_SCAN_SELECT:
> > chosen = p;
> > chosen_points = ULONG_MAX;
> > - /* fall through */
> > + break;
> > case OOM_SCAN_CONTINUE:
> > continue;
> > case OOM_SCAN_ABORT:
> > @@ -324,6 +324,8 @@ static struct task_struct *select_bad_process(unsigned int *ppoints,
> > case OOM_SCAN_OK:
> > break;
> > };
> > + if (chosen_points == ULONG_MAX)
> > + break;
> > points = oom_badness(p, NULL, nodemask, totalpages);
> > if (!points || points < chosen_points)
> > continue;
> > --
> > 1.7.10.4
> >
>
>
> --
> Michal Hocko
> SUSE Labs
As mentioned earlier, there's no need to keep iterating over all
running processes once the process with the highest score has been found.
--
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:[~2014-09-12 12:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 21:33 [PATCH] oom: break after selecting process to kill Niv Yehezkel
2014-09-12 1:22 ` 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 [this message]
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=20140912122143.GA20622@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.