Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757252Ab2EaGXd (ORCPT ); Thu, 31 May 2012 02:23:33 -0400 Received: from mail-qc0-f174.google.com ([209.85.216.174]:35568 "EHLO mail-qc0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753580Ab2EaGXb (ORCPT ); Thu, 31 May 2012 02:23:31 -0400 Message-ID: <4FC70E5E.1010003@gmail.com> Date: Thu, 31 May 2012 02:23:26 -0400 From: KOSAKI Motohiro User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: David Rientjes CC: Kamezawa Hiroyuki , 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> <4FC6D881.4090706@jp.fujitsu.com> <4FC70355.70805@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: 1369 Lines: 30 (5/31/12 2:17 AM), David Rientjes wrote: > 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. No. you don't need why userland folks want namespaces. Even though you don't need namespaces. It doesn't good reason to refuse another use case. -- 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/