From: Johannes Weiner <hannes@cmpxchg.org>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.cz>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch -mm] mm, oom: prefer thread group leaders for display purposes
Date: Thu, 16 Jan 2014 02:05:49 -0500 [thread overview]
Message-ID: <20140116070549.GL6963@cmpxchg.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1401151837560.1835@chino.kir.corp.google.com>
On Wed, Jan 15, 2014 at 06:40:41PM -0800, David Rientjes wrote:
> When two threads have the same badness score, it's preferable to kill the
> thread group leader so that the actual process name is printed to the
> kernel log rather than the thread group name which may be shared amongst
> several processes.
>
> This was the behavior when select_bad_process() used to do
> for_each_process(), but it now iterates threads instead and leads to
> ambiguity.
>
> Signed-off-by: David Rientjes <rientjes@google.com>
> ---
> mm/memcontrol.c | 18 +++++++++++-------
> mm/oom_kill.c | 12 ++++++++----
> 2 files changed, 19 insertions(+), 11 deletions(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index a815686..b482f49 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -1841,13 +1841,17 @@ static void mem_cgroup_out_of_memory(struct mem_cgroup *memcg, gfp_t gfp_mask,
> break;
> };
> points = oom_badness(task, memcg, NULL, totalpages);
> - if (points > chosen_points) {
> - if (chosen)
> - put_task_struct(chosen);
> - chosen = task;
> - chosen_points = points;
> - get_task_struct(chosen);
Where did that GET go?
> - }
> + if (points < chosen_points)
> + continue;
> + /* Prefer thread group leaders for display purposes */
> + if (points == chosen_points &&
> + thread_group_leader(chosen))
> + continue;
> +
> + if (chosen)
> + put_task_struct(chosen);
...boom.
> + chosen = task;
> + chosen_points = points;
> }
> css_task_iter_end(&it);
> }
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> index 054ff47..1dca3d8 100644
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -327,10 +327,14 @@ static struct task_struct *select_bad_process(unsigned int *ppoints,
> break;
> };
> points = oom_badness(p, NULL, nodemask, totalpages);
> - if (points > chosen_points) {
> - chosen = p;
> - chosen_points = points;
> - }
> + if (points < chosen_points)
> + continue;
> + /* Prefer thread group leaders for display purposes */
> + if (points == chosen_points && thread_group_leader(chosen))
> + continue;
> +
> + chosen = p;
> + chosen_points = points;
> }
> if (chosen)
> get_task_struct(chosen);
--
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-01-16 7:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 2:40 David Rientjes
2014-01-16 7:05 ` Johannes Weiner [this message]
2014-01-16 7:45 ` David Rientjes
2014-01-16 7:46 ` [patch v2 " David Rientjes
2014-01-16 14:21 ` Michal Hocko
2014-01-16 22:49 ` David Rientjes
2014-01-17 9:17 ` 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=20140116070549.GL6963@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--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