linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: balbir@linux.vnet.ibm.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
	"lizf@cn.fujitsu.com" <lizf@cn.fujitsu.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [-mm patch] Show memcg information during OOM
Date: Tue, 3 Feb 2009 10:21:57 +0900	[thread overview]
Message-ID: <20090203102157.9f643965.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20090202140849.GB918@balbir.in.ibm.com>

On Mon, 2 Feb 2009 19:38:49 +0530
Balbir Singh <balbir@linux.vnet.ibm.com> wrote:

> * Balbir Singh <balbir@linux.vnet.ibm.com> [2009-02-02 18:22:40]:
> 
> > Hi, All,
> > 
> > I found the following patch useful while debugging the memory
> > controller. It adds additional information if memcg invoked the OOM.
> > 
> > Comments, Suggestions?
> >
> 
> 
> Description: Add RSS and swap to OOM output from memcg
> 
> From: Balbir Singh <balbir@linux.vnet.ibm.com>
> 

> This patch displays memcg values like failcnt, usage and limit
> when an OOM occurs due to memcg.
> 

please use "KB" not bytes in OOM killer information.

And the most important information is dropped..
Even if you show information, the most important information that
"where I am and where we hit limit ?" is not coverred.
Could you consider some way to show full-path ?

  OOM-Killer:
  Task in /memory/xxx/yyy/zzz is killed by
  Limit of /memory/xxxx
  RSS Limit :     Usage:     Failcnt....
  RSS+SWAP Limit: ....



Thanks,
-Kame

--
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>

  reply	other threads:[~2009-02-03  1:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02 12:52 Balbir Singh
2009-02-02 12:59 ` KOSAKI Motohiro
2009-02-02 14:12   ` Balbir Singh
2009-02-02 14:17   ` Balbir Singh
2009-02-02 20:37     ` David Rientjes
2009-02-02 20:54       ` Balbir Singh
2009-02-02 21:05         ` David Rientjes
2009-02-03  4:41           ` Balbir Singh
2009-02-03  5:41           ` Balbir Singh
2009-02-03  5:45             ` David Rientjes
2009-02-02 13:45 ` Johannes Weiner
2009-02-03  3:44   ` Daisuke Nishimura
2009-02-03  5:55     ` Daisuke Nishimura
2009-02-03  6:04       ` David Rientjes
2009-02-02 14:08 ` Balbir Singh
2009-02-03  1:21   ` KAMEZAWA Hiroyuki [this message]
2009-02-03  4:34     ` Balbir Singh
2009-02-03  1:29   ` Li Zefan
2009-02-03  4:41     ` Balbir Singh
2009-02-03  4:47       ` David Rientjes
2009-02-03  4:55         ` Balbir Singh
2009-02-03  5:25           ` David Rientjes
2009-02-03  5:33             ` Balbir Singh
2009-02-03  5:24         ` Li Zefan
2009-02-03  5:35           ` Balbir Singh

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=20090203102157.9f643965.kamezawa.hiroyu@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=nishimura@mxp.nes.nec.co.jp \
    /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