[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090203043404.GK918@balbir.in.ibm.com>
Date: Tue, 3 Feb 2009 10:04:04 +0530
From: Balbir Singh <balbir@...ux.vnet.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"nishimura@....nes.nec.co.jp" <nishimura@....nes.nec.co.jp>,
"lizf@...fujitsu.com" <lizf@...fujitsu.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [-mm patch] Show memcg information during OOM
* KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> [2009-02-03 10:21:57]:
> On Mon, 2 Feb 2009 19:38:49 +0530
> Balbir Singh <balbir@...ux.vnet.ibm.com> wrote:
>
> > * Balbir Singh <balbir@...ux.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@...ux.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: ....
>
Sounds good to me, let me add this information.
--
Balbir
--
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