Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753683Ab2EaHKL (ORCPT ); Thu, 31 May 2012 03:10:11 -0400 Received: from mail-gh0-f180.google.com ([209.85.160.180]:32871 "EHLO mail-gh0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753407Ab2EaHKI convert rfc822-to-8bit (ORCPT ); Thu, 31 May 2012 03:10:08 -0400 MIME-Version: 1.0 In-Reply-To: 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> From: KOSAKI Motohiro Date: Thu, 31 May 2012 03:09:45 -0400 Message-ID: Subject: Re: [PATCH] meminfo: show /proc/meminfo base on container's memcg To: David Rientjes Cc: Kamezawa Hiroyuki , 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 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1607 Lines: 36 On Thu, May 31, 2012 at 2:56 AM, David Rientjes wrote: > On Thu, 31 May 2012, KOSAKI Motohiro wrote: > >> > This is tangent to the discussion, we need to revisit why an application >> > other than a daemon managing a set of memcgs would ever need to know the >> > information in /proc/meminfo. ?No use-case was ever presented in the >> > changelog and its not clear how this is at all relevant. ?So before >> > changing the kernel, please describe how this actually matters in a real- >> > world scenario. >> >> Huh? Don't you know a meanings of a namespace ISOLATION? isolation mean, >> isolated container shouldn't be able to access global information. If you >> want to lean container/namespace concept, tasting openvz or solaris container >> is a good start. > > As I said, LXC and namespace isolation is a tangent to the discussion of > faking the /proc/meminfo for the memcg context of a thread. Because of, /proc/meminfo affect a lot of libraries behavior. So, it's not only application issue. If you can't rewrite _all_ of userland assets, fake meminfo can't be escaped. Again see alternative container implementation. > >> But anyway, I dislike current implementaion. So, I NAK this patch too. >> > > I'm glad you reached that conclusion, but I think you did so for a much > different (although unspecified) reason. > > Thanks. -- 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/