From: Ying Han <yinghan@google.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Minchan Kim <minchan.kim@gmail.com>,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Tejun Heo <tj@kernel.org>, Pavel Emelyanov <xemul@openvz.org>,
Andrew Morton <akpm@linux-foundation.org>,
Li Zefan <lizf@cn.fujitsu.com>, Mel Gorman <mel@csn.ul.ie>,
Christoph Lameter <cl@linux.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Rik van Riel <riel@redhat.com>, Hugh Dickins <hughd@google.com>,
Michal Hocko <mhocko@suse.cz>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Zhu Yanhai <zhu.yanhai@gmail.com>,
linux-mm@kvack.org
Subject: Re: [PATCH V5] memcg: add memory.numastat api for numa statistics
Date: Mon, 23 May 2011 13:53:55 -0700 [thread overview]
Message-ID: <BANLkTikWT45NEQTArvwfb=DKYOmG3sL52Q@mail.gmail.com> (raw)
In-Reply-To: <20110523090816.3ab157d4.kamezawa.hiroyu@jp.fujitsu.com>
On Sun, May 22, 2011 at 5:08 PM, KAMEZAWA Hiroyuki
<kamezawa.hiroyu@jp.fujitsu.com> wrote:
> On Fri, 20 May 2011 15:01:58 -0700
> Ying Han <yinghan@google.com> wrote:
>
>> The new API exports numa_maps per-memcg basis. This is a piece of useful
>> information where it exports per-memcg page distribution across real numa
>> nodes.
>>
>> One of the usecase is evaluating application performance by combining this
>> information w/ the cpu allocation to the application.
>>
>> The output of the memory.numastat tries to follow w/ simiar format of numa_maps
>> like:
>>
>> total=<total pages> N0=<node 0 pages> N1=<node 1 pages> ...
>> file=<total file pages> N0=<node 0 pages> N1=<node 1 pages> ...
>> anon=<total anon pages> N0=<node 0 pages> N1=<node 1 pages> ...
>> unevictable=<total anon pages> N0=<node 0 pages> N1=<node 1 pages> ...
>>
>
> Ah, please update Documentaion please.
Sure, will send out patch for the Documentation.
--Ying
>
> 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/ .
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-05-23 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 22:01 [PATCH V5] memcg: add memory.numastat api for numa statistics Ying Han
2011-05-20 23:21 ` Rik van Riel
2011-05-23 0:08 ` KAMEZAWA Hiroyuki
2011-05-23 20:53 ` Ying Han [this message]
2011-05-24 15:46 ` Balbir Singh
2011-05-24 16:54 ` Ying Han
2011-05-25 3:25 ` 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='BANLkTikWT45NEQTArvwfb=DKYOmG3sL52Q@mail.gmail.com' \
--to=yinghan@google.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=cl@linux.com \
--cc=dave@linux.vnet.ibm.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=mel@csn.ul.ie \
--cc=mhocko@suse.cz \
--cc=minchan.kim@gmail.com \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=riel@redhat.com \
--cc=tj@kernel.org \
--cc=xemul@openvz.org \
--cc=zhu.yanhai@gmail.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;
as well as URLs for NNTP newsgroup(s).