From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail203.messagelabs.com (mail203.messagelabs.com [216.82.254.243]) by kanga.kvack.org (Postfix) with SMTP id 2DBF65F0001 for ; Wed, 8 Apr 2009 03:51:13 -0400 (EDT) Received: by rv-out-0708.google.com with SMTP id c5so2186929rvf.6 for ; Wed, 08 Apr 2009 00:52:00 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20090408163440.4442dc3c.kamezawa.hiroyu@jp.fujitsu.com> References: <20090407063722.GQ7082@balbir.in.ibm.com> <20090407172419.a5f318b9.kamezawa.hiroyu@jp.fujitsu.com> <20090408052904.GY7082@balbir.in.ibm.com> <20090408151529.fd6626c2.kamezawa.hiroyu@jp.fujitsu.com> <20090408070401.GC7082@balbir.in.ibm.com> <20090408160733.4813cb8d.kamezawa.hiroyu@jp.fujitsu.com> <20090408071115.GD7082@balbir.in.ibm.com> <20090408161824.26f47077.kamezawa.hiroyu@jp.fujitsu.com> <344eb09a0904080031y4406c001n584725b87024755@mail.gmail.com> <20090408163440.4442dc3c.kamezawa.hiroyu@jp.fujitsu.com> Date: Wed, 8 Apr 2009 13:15:01 +0530 Message-ID: <344eb09a0904080045s94c792dmc2250aaf39c09222@mail.gmail.com> Subject: Re: [RFI] Shared accounting for memory resource controller From: Bharata B Rao Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-linux-mm@kvack.org To: KAMEZAWA Hiroyuki Cc: balbir@linux.vnet.ibm.com, "linux-mm@kvack.org" , Andrew Morton , "lizf@cn.fujitsu.com" , Rik van Riel , Bharata B Rao , Dhaval Giani , KOSAKI Motohiro , "linux-kernel@vger.kernel.org" List-ID: On Wed, Apr 8, 2009 at 1:04 PM, KAMEZAWA Hiroyuki wrote: > On Wed, 8 Apr 2009 13:01:15 +0530 > Bharata B Rao wrote: > >> On Wed, Apr 8, 2009 at 12:48 PM, KAMEZAWA Hiroyuki >> wrote: >> > >> > On Wed, 8 Apr 2009 12:41:15 +0530 >> > Balbir Singh wrote: >> > > 3. Using the above, we can then try to (using an algorithm you >> > > proposed), try to do some work for figuring out the shared percentag= e. >> > > >> > This is the point. At last. Why "# of shared pages" is important ? >> > >> > I wonder it's better to add new stat file as memory.cacheinfo which he= lps >> > following kind of commands. >> > >> > =A0#cacheinfo /cgroups/memory/group01/ >> > =A0 =A0 =A0 /usr/lib/libc.so.1 =A0 =A0 30pages >> > =A0 =A0 =A0 /var/log/messages =A0 =A0 =A01 pages >> > =A0 =A0 =A0 /tmp/xxxxxx =A0 =A0 =A0 =A0 =A0 =A020 pages >> >> Can I suggest that we don't add new files for additional stats and try >> as far as possible to include them in .stat file. Please >> note that we have APIs in libcgroup library which can return >> statistics from controllers associated with a cgroup and these APIs >> assume that stats are part of .stat file. >> > Hmm ? Is there generic assumption as all cgroup has "stat" file ? No. But I would think if any controller has any stats to export, it would do so via .stat file. > And libcgroup cause bug if the new entry is added to stat file ? No. It can cope with new entries being added to stat file as long as they appear as (name, value) pairs. > (IOW, libcgroup can't ignore new entry added ?) It won't ignore, but can read the new stat. Regards, Bharata. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org