Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761644Ab2EQK6I (ORCPT ); Thu, 17 May 2012 06:58:08 -0400 Received: from mx2.parallels.com ([64.131.90.16]:46435 "EHLO mx2.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760981Ab2EQK6G (ORCPT ); Thu, 17 May 2012 06:58:06 -0400 Message-ID: <4FB4D945.7060108@parallels.com> Date: Thu, 17 May 2012 14:56:05 +0400 From: Glauber Costa User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1 MIME-Version: 1.0 To: KAMEZAWA Hiroyuki CC: Andrew Morton , Johannes Weiner , Michal Hocko , , , Subject: Re: [patch 6/6] mm: memcg: print statistics from live counters References: <1337018451-27359-1-git-send-email-hannes@cmpxchg.org> <1337018451-27359-7-git-send-email-hannes@cmpxchg.org> <20120516160131.fecb5ddf.akpm@linux-foundation.org> <4FB43FDB.6050300@jp.fujitsu.com> In-Reply-To: <4FB43FDB.6050300@jp.fujitsu.com> 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: 925 Lines: 19 On 05/17/2012 04:01 AM, KAMEZAWA Hiroyuki wrote: > Hm...sorry. I(fujitsu) am now considering to add meminfo for memcg..., > > add an option to override /proc/meminfo if a task is in container or > meminfo file somewhere. > (Now, we cannot trust /usr/bin/free, /usr/bin/top etc...in a container.) Yes, and all the previous times I tried to touch those, I think the general agreement was to come up with some kind of fuse overlay that would read information available from the kernel, and present it correctly formatted through bind-mounts on the files of interest. But that's mainly because we never reached agreement on how to make that appear automatically from such tasks -- 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/