From: David Rientjes <rientjes@google.com>
To: Frantisek Hrbata <fhrbata@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Minchan Kim <minchan.kim@gmail.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
CAI Qian <caiqian@redhat.com>,
lwoodman@redhat.com
Subject: Re: [PATCH] oom: add uid to "Killed process" message
Date: Tue, 21 Jun 2011 12:07:54 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1106211205290.30481@chino.kir.corp.google.com> (raw)
In-Reply-To: <20110621113629.GA2758@dhcp-26-164.brq.redhat.com>
On Tue, 21 Jun 2011, Frantisek Hrbata wrote:
> I guess the uid of the killed process can be identified from the dump_tasks
> output, where it is presented along with other info. I think it is handy
> to have the uid info directly in the "Killed process" message.
>
> This is used/requested by one of our customers and since I think it's a good
> idea to have the uid info presented, I posted the patch here to see what do you
> think about it.
>
I don't feel strongly about it, but I think you could justify adding a lot
of the same information from the tasklist dump to the single "Killed
process" message. The optimal way of getting this information would be
from the tasklist dump.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-06-21 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 11:04 Frantisek Hrbata
2011-06-20 21:09 ` David Rientjes
2011-06-21 11:36 ` Frantisek Hrbata
2011-06-21 19:07 ` David Rientjes [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-20 10:16 Frantisek Hrbata
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=alpine.DEB.2.00.1106211205290.30481@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=caiqian@redhat.com \
--cc=fhrbata@redhat.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lwoodman@redhat.com \
--cc=minchan.kim@gmail.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