Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757868Ab2EaCfw (ORCPT ); Wed, 30 May 2012 22:35:52 -0400 Received: from fgwmail5.fujitsu.co.jp ([192.51.44.35]:44928 "EHLO fgwmail5.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757705Ab2EaCfv (ORCPT ); Wed, 30 May 2012 22:35:51 -0400 X-SecurityPolicyCheck: OK by SHieldMailChecker v1.7.4 Message-ID: <4FC6D881.4090706@jp.fujitsu.com> Date: Thu, 31 May 2012 11:33:37 +0900 From: Kamezawa Hiroyuki User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: David Rientjes CC: KOSAKI Motohiro , Gao feng , 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> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; 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: 975 Lines: 30 (2012/05/31 10:31), David Rientjes wrote: > On Thu, 31 May 2012, Kamezawa Hiroyuki wrote: > >>>> My test with sysfs node's meminfo seems to work... >>>> >>>> [root@rx100-1 qqm]# mount --bind /sys/devices/system/node/node0/meminfo >>>> /proc/meminfo >>>> [root@rx100-1 qqm]# cat /proc/meminfo >>>> >>>> Node 0 MemTotal: 8379636 kB >>> >>> This doesn't seem like a good idea unless the application supports the >>> "Node 0" prefix in /proc/meminfo. >>> >> Of course, /cgroup/memory/..../memory.meminfo , a new file, will use the same >> format of /proc/meminfo. Above is just an example of bind-mount. >> > > It's not just a memcg issue, it would also be a cpusets issue. I think you can add cpuset.meminfo. Thanks, -Kame -- 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/