From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: kosaki.motohiro@jp.fujitsu.com,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>
Subject: Re: [RFC][PATCH] memcg: show real limit under hierarchy
Date: Thu, 11 Dec 2008 12:24:07 +0900 (JST) [thread overview]
Message-ID: <20081211122237.4FF7.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
In-Reply-To: <20081211121135.e00f6a2d.kamezawa.hiroyu@jp.fujitsu.com>
> I wonder other people who debugs memcg's hierarchy may use similar patches.
> this is my one.
> comments ?
> ==
> From:KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
>
> Show "real" limit of memcg.
> This helps my debugging and maybe useful for users.
>
> While testing hierarchy like this
>
> mount -t cgroup none /cgroup -t memory
> mkdir /cgroup/A
> set use_hierarchy==1 to "A"
> mkdir /cgroup/A/01
> mkdir /cgroup/A/01/02
> mkdir /cgroup/A/01/03
> mkdir /cgroup/A/01/03/04
> mkdir /cgroup/A/08
> mkdir /cgroup/A/08/01
> ....
> and set each own limit to them, "real" limit of each memcg is unclear.
> This patch shows real limit by checking all ancestors in memory.stat.
>
> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Great!
I hoped to use this patch at hierarchy inactive_ratio debugging ;)
next prev parent reply other threads:[~2008-12-11 3:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 3:11 KAMEZAWA Hiroyuki
2008-12-11 3:24 ` KOSAKI Motohiro [this message]
2008-12-11 14:00 ` Balbir Singh
2008-12-12 1:24 ` KAMEZAWA Hiroyuki
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=20081211122237.4FF7.KOSAKI.MOTOHIRO@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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