Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758133Ab2EaIe4 (ORCPT ); Thu, 31 May 2012 04:34:56 -0400 Received: from mx2.parallels.com ([64.131.90.16]:39915 "EHLO mx2.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932309Ab2EaIex (ORCPT ); Thu, 31 May 2012 04:34:53 -0400 Message-ID: <4FC72CA4.6080708@parallels.com> Date: Thu, 31 May 2012 12:32:36 +0400 From: Glauber Costa User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: Gao feng CC: KOSAKI Motohiro , David Rientjes , Kamezawa Hiroyuki , , , , , , , , Subject: Re: [PATCH] meminfo: show /proc/meminfo base on container's memcg References: <1338260214-21919-1-git-send-email-gaofeng@cn.fujitsu.com> <4FC6B68C.2070703@jp.fujitsu.com> <4FC6BC3E.5010807@jp.fujitsu.com> <4FC6C111.2060108@jp.fujitsu.com> <4FC6D881.4090706@jp.fujitsu.com> <4FC70355.70805@jp.fujitsu.com> <4FC70E5E.1010003@gmail.com> <4FC711A5.4090003@gmail.com> <4FC720EE.3010307@gmail.com> <4FC724B1.70508@cn.fujitsu.com> In-Reply-To: <4FC724B1.70508@cn.fujitsu.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1192 Lines: 25 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/