From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Paul Menage <menage@google.com>
Cc: YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
svaidy@linux.vnet.ibm.com, containers@lists.osdl.org,
minoura@valinux.co.jp,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [RFC] [PATCH] memory controller statistics
Date: Tue, 11 Sep 2007 08:09:55 +0530 [thread overview]
Message-ID: <46E5FFFB.8020805@linux.vnet.ibm.com> (raw)
In-Reply-To: <6599ad830709101621r2f1763cfpa0924f884d0ee2c@mail.gmail.com>
Paul Menage wrote:
> On 9/7/07, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>> Thanks for doing this. We are building containerstats for
>> per container statistics. It would be really nice to provide
>> the statistics using that interface. I am not opposed to
>> memory.stat, but Paul Menage recommends that one file has
>> just one meaningful value.
>
> That's based on examples from other virtual filesystems such as sysfs.
>
Even during the CKRM days (when configfs was used), the recommendation
from the configfs folks was the same. I sometimes worry about the
extra pinned dentries created with this logic/rule though.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
--
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:[~2007-09-11 2:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070907033942.4A6541BFA52@siro.lan>
2007-09-07 9:55 ` [RFC] [PATCH] memory controller statistics Balbir Singh
2007-09-10 0:32 ` 箕浦真
2007-09-10 8:26 ` Balbir Singh
2007-09-10 23:21 ` Paul Menage
2007-09-11 2:39 ` Balbir Singh [this message]
2007-09-26 1:48 ` YAMAMOTO Takashi
2007-09-26 3:16 ` 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=46E5FFFB.8020805@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=containers@lists.osdl.org \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=minoura@valinux.co.jp \
--cc=svaidy@linux.vnet.ibm.com \
--cc=yamamoto@valinux.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;
as well as URLs for NNTP newsgroup(s).