Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756987Ab2EaGSC (ORCPT ); Thu, 31 May 2012 02:18:02 -0400 Received: from mail-pz0-f46.google.com ([209.85.210.46]:64804 "EHLO mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753937Ab2EaGRy (ORCPT ); Thu, 31 May 2012 02:17:54 -0400 Date: Wed, 30 May 2012 23:17:51 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Kamezawa Hiroyuki 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 In-Reply-To: <4FC70355.70805@jp.fujitsu.com> Message-ID: 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> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1165 Lines: 25 On Thu, 31 May 2012, Kamezawa Hiroyuki wrote: > > The bottomline is that /proc/meminfo is one of many global resource state > > interfaces and doesn't imply that every thread has access to the full > > resources. It never has. It's very simple for another thread to consume > > a large amount of memory as soon as your read() of /proc/meminfo completes > > and then that information is completely bogus. > > Why you need to discuss this here ? We know all information are snapshot. > MemTotal is usually assumed to be static from /proc/meminfo and could now change radically without notification to the application. > Hmm....maybe need to mount cgroup in the container (again) and get an access > to cgroup > hierarchy and find the cgroup it belongs to......if it's allowed. An application should always know the cgroup that its attached to and be able to read its state using the command that I gave earlier. -- 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/