From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756431Ab1KCRg3 (ORCPT ); Thu, 3 Nov 2011 13:36:29 -0400 Received: from mx2.parallels.com ([64.131.90.16]:51956 "EHLO mx2.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755829Ab1KCRg2 (ORCPT ); Thu, 3 Nov 2011 13:36:28 -0400 Message-ID: <4EB2D0F2.40309@parallels.com> Date: Thu, 3 Nov 2011 15:35:46 -0200 From: Glauber Costa User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20110927 Thunderbird/7.0 MIME-Version: 1.0 To: Paul Menage CC: Frederic Weisbecker , Glauber Costa , Andrew Morton , Tim Hockin , LKML , Li Zefan , Johannes Weiner , Aditya Kali , Oleg Nesterov , Kay Sievers , Tejun Heo , "Kirill A. Shutemov" , Containers , Paul Turner Subject: Re: [PATCH 00/10] cgroups: Task counter subsystem v6 References: <1317668832-10784-1-git-send-email-fweisbec@gmail.com> <20111004150111.e9337268.akpm00@gmail.com> <20111028163021.1ce61f8a.akpm@linux-foundation.org> <20111103164917.GF8198@somewhere.redhat.com> <4EB2C852.6020706@parallels.com> <4EB2CA03.7030601@parallels.com> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [201.82.130.234] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/03/2011 03:28 PM, Paul Menage wrote: > On Thu, Nov 3, 2011 at 10:06 AM, Glauber Costa wrote: >> Sorry if I wasn't clear: It removes the need to walk multiple independent >> hierarchies. The walk is done only once. > > You're talking about at fork time, and the concern is the cache > footprint involved in walking up the parent pointer chain? Yes, we can say this is my main concern. > Isn't that an argument against multiple hierarchies (which is a > decision for the admin), rather than against more subsystem > flexibility? Not always it is a decision for the admin. In most cases, it is a constraint of the problem. For containers - take lxc as an example, the most reasonable thing to do is to grab all cgroups subsystems available, and contain them. > If multiple subsystems on the same hierarchy each need to > walk up the pointer chain on the same event, then after the first > subsystem has done so the chain will be in cache for any subsequent > walks from other subsystems. No, it won't. Precisely because different subsystems have completely independent pointer chains.