From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
To: Michal Hocko <mhocko@suse.cz>
Cc: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] memcg: update documentation to describe usage_in_bytes
Date: Wed, 20 Apr 2011 08:24:34 +0900 [thread overview]
Message-ID: <20110420082434.55839f06.nishimura@mxp.nes.nec.co.jp> (raw)
In-Reply-To: <20110419121414.GF21689@tiehlicka.suse.cz>
Hi,
On Tue, 19 Apr 2011 14:14:14 +0200
Michal Hocko <mhocko@suse.cz> wrote:
> Hi,
>
> On Tue 29-03-11 09:21:22, Michal Hocko wrote:
> > On Tue 29-03-11 10:15:11, Daisuke Nishimura wrote:
> > [...]
> > > From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
> > >
> > > Since 569b846d(memcg: coalesce uncharge during unmap/truncate), we do batched
> > > (delayed) uncharge at truncation/unmap. And since cdec2e42(memcg: coalesce
> > > charging via percpu storage), we have percpu cache for res_counter.
> > >
> > > These changes improved performance of memory cgroup very much, but made
> > > res_counter->usage usually have a bigger value than the actual value of memory usage.
> > > So, *.usage_in_bytes, which show res_counter->usage, are not desirable for precise
> > > values of memory(and swap) usage anymore.
> > >
> > > Instead of removing these files completely(because we cannot know res_counter->usage
> > > without them), this patch updates the meaning of those files.
> > >
> > > Signed-off-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
> > > ---
> > > Documentation/cgroups/memory.txt | 15 +++++++++++++--
> > > 1 files changed, 13 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/Documentation/cgroups/memory.txt b/Documentation/cgroups/memory.txt
> > > index 7781857..4f49d91 100644
> > > --- a/Documentation/cgroups/memory.txt
> > > +++ b/Documentation/cgroups/memory.txt
> > > @@ -52,8 +52,10 @@ Brief summary of control files.
> > > tasks # attach a task(thread) and show list of threads
> > > cgroup.procs # show list of processes
> > > cgroup.event_control # an interface for event_fd()
> > > - memory.usage_in_bytes # show current memory(RSS+Cache) usage.
> > > - memory.memsw.usage_in_bytes # show current memory+Swap usage
> > > + memory.usage_in_bytes # show current res_counter usage for memory
> > > + (See 5.5 for details)
> > > + memory.memsw.usage_in_bytes # show current res_counter usage for memory+Swap
> > > + (See 5.5 for details)
> > > memory.limit_in_bytes # set/show limit of memory usage
> > > memory.memsw.limit_in_bytes # set/show limit of memory+Swap usage
> > > memory.failcnt # show the number of memory usage hits limits
> > > @@ -453,6 +455,15 @@ memory under it will be reclaimed.
> > > You can reset failcnt by writing 0 to failcnt file.
> > > # echo 0 > .../memory.failcnt
> > >
> > > +5.5 usage_in_bytes
> > > +
> > > +For efficiency, as other kernel components, memory cgroup uses some optimization
> > > +to avoid unnecessary cacheline false sharing. usage_in_bytes is affected by the
> > > +method and doesn't show 'exact' value of memory(and swap) usage, it's an fuzz
> > > +value for efficient access. (Of course, when necessary, it's synchronized.)
> > > +If you want to know more exact memory usage, you should use RSS+CACHE(+SWAP)
> > > +value in memory.stat(see 5.2).
> > > +
> > > 6. Hierarchy support
> > >
> > > The memory controller supports a deep hierarchy and hierarchical accounting.
> >
> > Acked-by: Michal Hocko <mhocko@suse.cz>
> >
> > Although I would like to see a mention about what is the reason for
> > keeping that file(s) if their usage is very limited. Something like.
> > "We are keeping the file because we want to be consistent with other
> > cgroups implementations and all of them export usage counter in some
> > way. Make sure you exactly know the meaning before you use the value
> > in userspace."
> >
> > If nobody else feels that this is that important then please forget
> > about this comment.
>
> I am wondering what happened to the patch. Do you have any plans to
> update/push it?
>
Ouch! Thank you for your reminding me..
I'll resend this to Andrew soon.
Thanks,
Daisuke Nishimura.
--
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-04-19 23:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 15:25 cgroup: real meaning of memory.usage_in_bytes Michal Hocko
2011-03-18 15:29 ` Michal Hocko
2011-03-21 9:34 ` Michal Hocko
2011-03-21 10:24 ` [PATCH] memcg: consider per-cpu stock reserves when returning RES_USAGE for _MEM Michal Hocko
2011-03-22 0:10 ` KAMEZAWA Hiroyuki
2011-03-22 1:47 ` Daisuke Nishimura
2011-03-22 7:31 ` Michal Hocko
2011-03-23 0:27 ` Daisuke Nishimura
2011-03-23 4:35 ` KAMEZAWA Hiroyuki
2011-03-27 23:55 ` Daisuke Nishimura
2011-03-28 4:25 ` [PATCH] memcg: update documentation to describe usage_in_bytes Daisuke Nishimura
2011-03-28 7:43 ` Michal Hocko
2011-03-28 9:11 ` KAMEZAWA Hiroyuki
2011-03-28 9:48 ` Michal Hocko
2011-03-28 10:31 ` KAMEZAWA Hiroyuki
2011-03-29 1:15 ` [PATCH v2] " Daisuke Nishimura
2011-03-29 1:24 ` KAMEZAWA Hiroyuki
2011-03-29 7:21 ` Michal Hocko
2011-04-19 12:14 ` Michal Hocko
2011-04-19 23:24 ` Daisuke Nishimura [this message]
2011-03-21 17:22 ` cgroup: real meaning of memory.usage_in_bytes Ying Han
2011-03-22 7:35 ` Michal Hocko
2011-03-22 17:06 ` Ying Han
2011-03-23 14:26 ` Michal Hocko
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=20110420082434.55839f06.nishimura@mxp.nes.nec.co.jp \
--to=nishimura@mxp.nes.nec.co.jp \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).