From: Glauber Costa <glommer@parallels.com>
To: Gao feng <gaofeng@cn.fujitsu.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
David Rientjes <rientjes@google.com>,
Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
hannes@cmpxchg.org, mhocko@suse.cz, bsingharora@gmail.com,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
cgroups@vger.kernel.org, linux-mm@kvack.org,
containers@lists.linux-foundation.org
Subject: Re: [PATCH] meminfo: show /proc/meminfo base on container's memcg
Date: Thu, 31 May 2012 12:32:36 +0400 [thread overview]
Message-ID: <4FC72CA4.6080708@parallels.com> (raw)
In-Reply-To: <4FC724B1.70508@cn.fujitsu.com>
On 05/31/2012 11:58 AM, Gao feng wrote:
>> > It's one of a option. But, I seriously doubt fuse can make simpler than kamezawa-san's
>> > idea. But yeah, I might NACK kamezawa-san's one if he will post ugly patch.
>> >
> It seams I should do some homework to make the implement beautifully.
>
> I think kamezawa-san's idea is more simpler.
> thanks for your advice.
>
One think to keep in mind: A file in memcg does not need to follow the
same format of /proc/meminfo so we can bind mount. We should be able to
reconstruct that in userspace based on information available from the
kernel. You can even collect that from multiple locations, and *then*
you bind mount.
It helps to keep the churn out of the kernel, and in case of meminfo,
you might need no extra kernel patches at all. And in the case of other
files like /proc/stat, the relevant information comes from more than one
cgroup anyway, so there is not too much way around it.
--
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:[~2012-05-31 8:34 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 2:56 Gao feng
2012-05-29 8:24 ` Glauber Costa
2012-05-30 21:38 ` David Rientjes
2012-05-30 23:20 ` Kirill A. Shutemov
2012-05-31 0:35 ` David Rientjes
2012-05-31 0:08 ` Kamezawa Hiroyuki
2012-05-31 0:22 ` KOSAKI Motohiro
2012-05-31 0:33 ` Kamezawa Hiroyuki
2012-05-31 0:44 ` David Rientjes
2012-05-31 0:53 ` Kamezawa Hiroyuki
2012-05-31 1:31 ` David Rientjes
2012-05-31 2:33 ` Kamezawa Hiroyuki
2012-05-31 5:02 ` David Rientjes
2012-05-31 5:36 ` Kamezawa Hiroyuki
2012-05-31 6:17 ` David Rientjes
2012-05-31 6:23 ` KOSAKI Motohiro
2012-05-31 6:28 ` David Rientjes
2012-05-31 6:37 ` KOSAKI Motohiro
2012-05-31 6:56 ` David Rientjes
2012-05-31 7:09 ` KOSAKI Motohiro
2012-05-31 7:35 ` David Rientjes
2012-05-31 7:42 ` KOSAKI Motohiro
2012-05-31 7:57 ` Johannes Weiner
2012-05-31 7:58 ` Gao feng
2012-05-31 8:32 ` Glauber Costa [this message]
2012-05-31 8:51 ` Kamezawa Hiroyuki
2012-05-31 8:59 ` Glauber Costa
2012-05-31 8:55 ` Gao feng
2012-05-31 8:56 ` Glauber Costa
2012-05-31 7:07 ` Kamezawa Hiroyuki
2012-05-31 7:23 ` KOSAKI Motohiro
2012-05-31 8:29 ` Glauber Costa
2012-06-07 23:18 ` Zhu Yanhai
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=4FC72CA4.6080708@parallels.com \
--to=glommer@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=gaofeng@cn.fujitsu.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=rientjes@google.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