From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Bharata B Rao <bharata.rao@gmail.com>
Cc: balbir@linux.vnet.ibm.com,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
"lizf@cn.fujitsu.com" <lizf@cn.fujitsu.com>,
Rik van Riel <riel@surriel.com>,
Bharata B Rao <bharata.rao@in.ibm.com>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFI] Shared accounting for memory resource controller
Date: Wed, 8 Apr 2009 16:34:40 +0900 [thread overview]
Message-ID: <20090408163440.4442dc3c.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <344eb09a0904080031y4406c001n584725b87024755@mail.gmail.com>
On Wed, 8 Apr 2009 13:01:15 +0530
Bharata B Rao <bharata.rao@gmail.com> wrote:
> On Wed, Apr 8, 2009 at 12:48 PM, KAMEZAWA Hiroyuki
> <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> >
> > On Wed, 8 Apr 2009 12:41:15 +0530
> > Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> > > 3. Using the above, we can then try to (using an algorithm you
> > > proposed), try to do some work for figuring out the shared percentage.
> > >
> > This is the point. At last. Why "# of shared pages" is important ?
> >
> > I wonder it's better to add new stat file as memory.cacheinfo which helps
> > following kind of commands.
> >
> > A #cacheinfo /cgroups/memory/group01/
> > A A A /usr/lib/libc.so.1 A A 30pages
> > A A A /var/log/messages A A A 1 pages
> > A A A /tmp/xxxxxx A A A A A A 20 pages
>
> Can I suggest that we don't add new files for additional stats and try
> as far as possible to include them in <controller>.stat file. Please
> note that we have APIs in libcgroup library which can return
> statistics from controllers associated with a cgroup and these APIs
> assume that stats are part of <controller>.stat file.
>
Hmm ? Is there generic assumption as all cgroup has "stat" file ?
And libcgroup cause bug if the new entry is added to stat file ?
(IOW, libcgroup can't ignore new entry added ?)
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:[~2009-04-08 7:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 6:37 Balbir Singh
2009-04-07 7:00 ` KAMEZAWA Hiroyuki
2009-04-07 7:18 ` Balbir Singh
2009-04-07 7:33 ` KAMEZAWA Hiroyuki
2009-04-07 8:03 ` Balbir Singh
2009-04-07 8:24 ` KAMEZAWA Hiroyuki
2009-04-07 10:10 ` Balbir Singh
2009-04-08 5:29 ` Balbir Singh
2009-04-08 6:15 ` KAMEZAWA Hiroyuki
2009-04-08 7:04 ` Balbir Singh
2009-04-08 7:07 ` KAMEZAWA Hiroyuki
2009-04-08 7:11 ` Balbir Singh
2009-04-08 7:18 ` KAMEZAWA Hiroyuki
2009-04-08 7:31 ` Bharata B Rao
2009-04-08 7:34 ` KAMEZAWA Hiroyuki [this message]
2009-04-08 7:45 ` Bharata B Rao
2009-04-08 7:52 ` Dhaval Giani
2009-04-08 7:39 ` KAMEZAWA Hiroyuki
2009-04-08 7:48 ` Balbir Singh
2009-04-08 8:03 ` KAMEZAWA Hiroyuki
2009-04-08 8:49 ` Balbir Singh
2009-04-08 8:54 ` KAMEZAWA Hiroyuki
2009-04-08 9:02 ` 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=20090408163440.4442dc3c.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=bharata.rao@gmail.com \
--cc=bharata.rao@in.ibm.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=riel@surriel.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