[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1401161447510.31228@chino.kir.corp.google.com>
Date: Thu, 16 Jan 2014 14:49:25 -0800 (PST)
From: David Rientjes <rientjes@...gle.com>
To: Michal Hocko <mhocko@...e.cz>
cc: Andrew Morton <akpm@...ux-foundation.org>,
Johannes Weiner <hannes@...xchg.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
cgroups@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [patch v2 -mm] mm, oom: prefer thread group leaders for display
purposes
On Thu, 16 Jan 2014, Michal Hocko 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.
>
> I am not sure I understand this. Is this about ->comm? If yes then why
> couldn't the group leader do PR_SET_NAME?
>
Both comm and pid, we only display thread group leaders in the tasklist
dump of eligible processes, we want the killed message to specify from
which process.
You're suggesting a thread group leader do PR_SET_NAME of all its threads
for readable oom killer output? Lol.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists