From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755514Ab2IXNry (ORCPT ); Mon, 24 Sep 2012 09:47:54 -0400 Received: from mx2.parallels.com ([64.131.90.16]:48359 "EHLO mx2.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754136Ab2IXNrw (ORCPT ); Mon, 24 Sep 2012 09:47:52 -0400 Message-ID: <506063B8.70305@parallels.com> Date: Mon, 24 Sep 2012 17:44:24 +0400 From: Glauber Costa User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120828 Thunderbird/15.0 MIME-Version: 1.0 To: Christoph Lameter CC: Tejun Heo , "" , "" , "" , "" , "" , Suleiman Souhlal , Frederic Weisbecker , Mel Gorman , David Rientjes , Pekka Enberg , Michal Hocko , Johannes Weiner Subject: Re: [PATCH v3 05/16] consider a memcg parameter in kmem_create_cache References: <1347977530-29755-1-git-send-email-glommer@parallels.com> <1347977530-29755-6-git-send-email-glommer@parallels.com> <20120921181458.GG7264@google.com> <506015E7.8030900@parallels.com> <00000139f84bdedc-aae672a6-2908-4cb8-8ed3-8fedf67a21af-000000@email.amazonses.com> <50605500.5050606@parallels.com> <00000139f8836571-6ddc9d5b-1d5f-4542-92f9-ad11070e5b7d-000000@email.amazonses.com> In-Reply-To: <00000139f8836571-6ddc9d5b-1d5f-4542-92f9-ad11070e5b7d-000000@email.amazonses.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/24/2012 05:42 PM, Christoph Lameter wrote: > On Mon, 24 Sep 2012, Glauber Costa wrote: > >> But that is orthogonal, isn't it? People will still expect to see it in >> the old slabinfo file. > > The current scheme for memory statistics is > > /proc/meminfo contains global counters > > /sys/devices/system/node/nodeX/meminfo > > contains node specific counters. > > The cgroups directory already contains various files. Adding a slabinfo > file would make sense and it could be found easily. > > The sysfs hierachy /sys/kernel/slab could also show up there as a "slab" > directory under which all the details of the various caches would be > available and tunable. Very much in sync with the way the cgroups > directories operate. > The reason I say it is orthogonal, is that people will still want to see their caches in /proc/slabinfo, regardless of wherever else they'll be. It was a requirement from Pekka in one of the first times I posted this, IIRC.