From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: balbir@linux.vnet.ibm.com
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
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>
Subject: Re: [RFC] Shared page accounting for memory cgroup
Date: Fri, 8 Jan 2010 08:47:27 +0900 [thread overview]
Message-ID: <20100108084727.429c40fc.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20100107092736.GW3059@balbir.in.ibm.com>
On Thu, 7 Jan 2010 14:57:36 +0530
Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> * KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> [2010-01-07 18:08:00]:
>
> > On Thu, 7 Jan 2010 17:48:14 +0900
> > KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> > > > > "How pages are shared" doesn't show good hints. I don't hear such parameter
> > > > > is used in production's resource monitoring software.
> > > > >
> > > >
> > > > You mean "How many pages are shared" are not good hints, please see my
> > > > justification above. With Virtualization (look at KSM for example),
> > > > shared pages are going to be increasingly important part of the
> > > > accounting.
> > > >
> > >
> > > Considering KSM, your cuounting style is tooo bad.
> > >
> > > You should add
> > >
> > > - MEM_CGROUP_STAT_SHARED_BY_KSM
> > > - MEM_CGROUP_STAT_FOR_TMPFS/SYSV_IPC_SHMEM
> > >
>
> No.. I am just talking about shared memory being important and shared
> accounting being useful, no counters for KSM in particular (in the
> memcg context).
>
Think so ? The number of memcg-private pages is in interest in my point of view.
Anyway, I don't change my opinion as "sum of rss" is not necessary to be calculated
in the kernel.
If you want to provide that in memcg, please add it to global VM as /proc/meminfo.
IIUC, KSM/SHMEM has some official method in global VM.
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>
next prev parent reply other threads:[~2010-01-07 23:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 18:27 Balbir Singh
2010-01-03 23:51 ` KAMEZAWA Hiroyuki
2010-01-04 0:07 ` Balbir Singh
2010-01-04 0:35 ` KAMEZAWA Hiroyuki
2010-01-04 0:50 ` Balbir Singh
2010-01-06 4:02 ` KAMEZAWA Hiroyuki
2010-01-06 7:01 ` Balbir Singh
2010-01-06 7:12 ` KAMEZAWA Hiroyuki
2010-01-07 7:15 ` Balbir Singh
2010-01-07 7:36 ` KAMEZAWA Hiroyuki
2010-01-07 8:34 ` Balbir Singh
2010-01-07 8:48 ` KAMEZAWA Hiroyuki
2010-01-07 9:08 ` KAMEZAWA Hiroyuki
2010-01-07 9:27 ` Balbir Singh
2010-01-07 23:47 ` KAMEZAWA Hiroyuki [this message]
2010-01-17 19:30 ` Balbir Singh
2010-01-18 0:05 ` KAMEZAWA Hiroyuki
2010-01-18 0:22 ` KAMEZAWA Hiroyuki
2010-01-18 0:49 ` Daisuke Nishimura
2010-01-18 8:26 ` Balbir Singh
2010-01-19 1:22 ` Daisuke Nishimura
2010-01-19 1:49 ` Balbir Singh
2010-01-19 2:34 ` Daisuke Nishimura
2010-01-19 3:52 ` Balbir Singh
2010-01-20 4:09 ` Daisuke Nishimura
2010-01-20 7:15 ` Daisuke Nishimura
2010-01-20 7:43 ` KAMEZAWA Hiroyuki
2010-01-20 8:18 ` Balbir Singh
2010-01-20 8:17 ` Balbir Singh
2010-01-21 1:04 ` Daisuke Nishimura
2010-01-21 1:30 ` 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=20100108084727.429c40fc.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=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