From: David Rientjes <rientjes@google.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, caiqian@redhat.com, hughd@google.com,
kamezawa.hiroyu@jp.fujitsu.com, minchan.kim@gmail.com,
oleg@redhat.com
Subject: Re: [PATCH 2/6] oom: improve dump_tasks() show items
Date: Wed, 22 Jun 2011 15:59:40 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1106221558160.11759@chino.kir.corp.google.com> (raw)
In-Reply-To: <4E01C82A.7070702@jp.fujitsu.com>
On Wed, 22 Jun 2011, KOSAKI Motohiro wrote:
> Recently, oom internal logic was dramatically changed. Thus
> dump_tasks() doesn't show enough information for bug report
> analysis. it has some meaningless items and don't have some
> oom socre related items.
>
> This patch adapt displaying fields to new oom logic.
>
> details
> --------
> removed: pid (we always kill process. don't need thread id),
> signal->oom_adj (we no longer uses it internally)
> cpu (we no longer uses it)
> added: ppid (we often kill sacrifice child process)
> swap (it's accounted)
> modify: RSS (account mm->nr_ptes too)
>
> <old>
> [ pid ] uid tgid total_vm rss cpu oom_adj oom_score_adj name
> [ 3886] 0 3886 2893 441 1 0 0 bash
> [ 3905] 0 3905 29361 25833 0 0 0 memtoy
>
> <new>
> [ pid] ppid uid euid total_vm rss swap score_adj name
> [ 417] 1 0 0 3298 12 184 -1000 udevd
> [ 830] 1 0 0 1776 11 16 0 system-setup-ke
> [ 973] 1 0 0 61179 35 116 0 rsyslogd
> [ 1733] 1732 0 0 1052337 958582 0 0 memtoy
>
I like this very much! I'm always supportive of providing additional
information that will allow users to investigate oom conditions more
thoroughly.
I'm not sure that we should be exporting the euid, however, since I
disagreed with using it in the badness heuristic of the first patch.
Let's talk about it there and then perhaps it can be removed from the
tasklist dump if we don't actually end up using it?
Otherwise, it looks good!
--
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-22 22:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 10:45 [PATCH v3 0/6] Fix oom killer doesn't work at all if system have > gigabytes memory (aka CAI founded issue) KOSAKI Motohiro
2011-06-22 10:46 ` [PATCH 1/6] oom: use euid instead of CAP_SYS_ADMIN for protection root process KOSAKI Motohiro
2011-06-22 22:57 ` David Rientjes
2011-06-22 10:47 ` [PATCH 2/6] oom: improve dump_tasks() show items KOSAKI Motohiro
2011-06-22 22:59 ` David Rientjes [this message]
2011-06-22 10:47 ` [PATCH 3/6] oom: kill younger process first KOSAKI Motohiro
2011-06-22 23:01 ` David Rientjes
2011-06-22 10:48 ` [PATCH 4/6] oom: oom-killer don't use proportion of system-ram internally KOSAKI Motohiro
2011-06-22 23:16 ` David Rientjes
2011-06-22 10:48 ` [PATCH 5/6] oom: don't kill random process KOSAKI Motohiro
2011-06-22 23:22 ` David Rientjes
2011-06-22 10:49 ` [PATCH 6/6] oom: merge oom_kill_process() with oom_kill_task() KOSAKI Motohiro
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.1106221558160.11759@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=caiqian@redhat.com \
--cc=hughd@google.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=minchan.kim@gmail.com \
--cc=oleg@redhat.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