[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FC73110.6010107@jp.fujitsu.com>
Date: Thu, 31 May 2012 17:51:28 +0900
From: Kamezawa Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To: Glauber Costa <glommer@...allels.com>
CC: Gao feng <gaofeng@...fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@...il.com>,
David Rientjes <rientjes@...gle.com>, hannes@...xchg.org,
mhocko@...e.cz, bsingharora@...il.com, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, cgroups@...r.kernel.org,
linux-mm@...ck.org, containers@...ts.linux-foundation.org
Subject: Re: [PATCH] meminfo: show /proc/meminfo base on container's memcg
(2012/05/31 17:32), Glauber Costa wrote:
> 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.
I'm sorry I couldn't fully understand. Could you explain more ?
Do you mean
- bind mount memory cgroup directory into the container for exporting information
- Some user-space apps, FUSE-procfs or some, can provide enough information
?
Thanks,
-Kame
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists