From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gao feng Subject: Re: [PATCH] meminfo: show /proc/meminfo base on container's memcg Date: Thu, 31 May 2012 16:55:31 +0800 Message-ID: <4FC73203.2070009@cn.fujitsu.com> 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> <4FC72CA4.6080708@parallels.com> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4FC72CA4.6080708@parallels.com> Sender: owner-linux-mm@kvack.org List-ID: Content-Type: text/plain; charset="utf-8" To: Glauber Costa Cc: KOSAKI Motohiro , David Rientjes , Kamezawa Hiroyuki , 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 =E4=BA=8E 2012=E5=B9=B405=E6=9C=8831=E6=97=A5 16:32, Glauber Costa =E5=86= =99=E9=81=93: > On 05/31/2012 11:58 AM, Gao feng wrote: >>> > It's one of a option. But, I seriously doubt fuse can make simpler t= han 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. >> >=20 > One think to keep in mind: A file in memcg does not need to follow the sa= me format of /proc/meminfo so we can bind mount. We should be able to recon= struct that in userspace based on information > available from the kernel. You can even collect that from multiple locati= ons, and *then* you bind mount. >=20 > 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. I got it,thank you very much,indeed we need no extra kernel patch at all. Maybe we should do this work in lxc or libvirt. thanks Glauber! = -- 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: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx155.postini.com [74.125.245.155]) by kanga.kvack.org (Postfix) with SMTP id 6D3E96B005D for ; Thu, 31 May 2012 04:54:59 -0400 (EDT) Message-ID: <4FC73203.2070009@cn.fujitsu.com> Date: Thu, 31 May 2012 16:55:31 +0800 From: Gao feng MIME-Version: 1.0 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> <4FC72CA4.6080708@parallels.com> In-Reply-To: <4FC72CA4.6080708@parallels.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Sender: owner-linux-mm@kvack.org List-ID: To: Glauber Costa Cc: KOSAKI Motohiro , David Rientjes , Kamezawa Hiroyuki , 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 =E4=BA=8E 2012=E5=B9=B405=E6=9C=8831=E6=97=A5 16:32, Glauber Costa =E5=86= =99=E9=81=93: > On 05/31/2012 11:58 AM, Gao feng wrote: >>> > It's one of a option. But, I seriously doubt fuse can make simpler t= han 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. >> >=20 > One think to keep in mind: A file in memcg does not need to follow the sa= me format of /proc/meminfo so we can bind mount. We should be able to recon= struct that in userspace based on information > available from the kernel. You can even collect that from multiple locati= ons, and *then* you bind mount. >=20 > 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. I got it,thank you very much,indeed we need no extra kernel patch at all. Maybe we should do this work in lxc or libvirt. thanks Glauber! = -- 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: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752329Ab2EaIzD (ORCPT ); Thu, 31 May 2012 04:55:03 -0400 Received: from cn.fujitsu.com ([222.73.24.84]:58701 "EHLO song.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1751530Ab2EaIzA convert rfc822-to-8bit (ORCPT ); Thu, 31 May 2012 04:55:00 -0400 X-IronPort-AV: E=Sophos;i="4.75,691,1330876800"; d="scan'208";a="5084577" Message-ID: <4FC73203.2070009@cn.fujitsu.com> Date: Thu, 31 May 2012 16:55:31 +0800 From: Gao feng User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: Glauber Costa CC: KOSAKI Motohiro , David Rientjes , Kamezawa Hiroyuki , 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 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> <4FC72CA4.6080708@parallels.com> In-Reply-To: <4FC72CA4.6080708@parallels.com> X-MIMETrack: Itemize by SMTP Server on mailserver/fnst(Release 8.5.3|September 15, 2011) at 2012/05/31 16:53:04, Serialize by Router on mailserver/fnst(Release 8.5.3|September 15, 2011) at 2012/05/31 16:53:07 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 于 2012年05月31日 16:32, Glauber Costa 写道: > 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. I got it,thank you very much,indeed we need no extra kernel patch at all. Maybe we should do this work in lxc or libvirt. thanks Glauber!