linux-kernel - Re: [PATCH] meminfo: show /proc/meminfo base on container's memcg

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4FC72CA4.6080708@parallels.com>
Date:	Thu, 31 May 2012 12:32:36 +0400
From:	Glauber Costa <glommer@...allels.com>
To:	Gao feng <gaofeng@...fujitsu.com>
CC:	KOSAKI Motohiro <kosaki.motohiro@...il.com>,
	David Rientjes <rientjes@...gle.com>,
	Kamezawa Hiroyuki <kamezawa.hiroyu@...fujitsu.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

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 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/