From: Niv Yehezkel <executerx@gmail.com>
To: Zhang Zhen <zhenzhang.zhang@huawei.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
rientjes@google.com, mhocko@suse.cz, hannes@cmpxchg.org,
oleg@redhat.com, wangnan0@huawei.com
Subject: Re: [PATCH] oom: break after selecting process to kill
Date: Fri, 12 Sep 2014 03:39:36 -0400 [thread overview]
Message-ID: <20140912073936.GA10692@localhost.localdomain> (raw)
In-Reply-To: <54124AC9.2040308@huawei.com>
On Fri, Sep 12, 2014 at 09:22:17AM +0800, Zhang Zhen wrote:
> On 2014/9/12 5:33, Niv Yehezkel wrote:
> > 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;
>
> Hi,
> The following comment shows that we prefer thread group leaders for display purposes.
> If we break here and two threads in a thread group are performing the swapoff syscall, maybe we can not get thread
> group leaders.
>
> Thanks!
>
> > points = oom_badness(p, NULL, nodemask, totalpages);
> > if (!points || points < chosen_points)
> > continue;
> >
>
>
Well, this is not the logic implemented in the loop.
Once a process is selected, it fallbacks and continues the loop.
If two threads are performing the swapoff, the latter will be chosen whatsoever.
--
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 7:39 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 [this message]
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=20140912073936.GA10692@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 \
--cc=wangnan0@huawei.com \
--cc=zhenzhang.zhang@huawei.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).