From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Hocko Subject: Re: [patch v2 -mm] mm, oom: prefer thread group leaders for display purposes Date: Fri, 17 Jan 2014 10:17:06 +0100 Message-ID: <20140117091706.GA5356@dhcp22.suse.cz> References: <20140116070549.GL6963@cmpxchg.org> <20140116142141.GF28157@dhcp22.suse.cz> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: David Rientjes Cc: Andrew Morton , Johannes Weiner , KAMEZAWA Hiroyuki , cgroups@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org On Thu 16-01-14 14:49:25, David Rientjes wrote: > 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. OK, that makes sense now. I didn't think about dump_tasks and consistency in the output. > You're suggesting a thread group leader do PR_SET_NAME of all its threads > for readable oom killer output? Lol. No, I am not suggesting anything. I was just asking why is group leader different in this regards becasue changelog didn't tell it and I didn't put it together with dump_tasks. Thanks! -- Michal Hocko SUSE Labs -- 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: email@kvack.org