From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752904Ab2IFMSq (ORCPT ); Thu, 6 Sep 2012 08:18:46 -0400 Received: from cantor2.suse.de ([195.135.220.15]:38665 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751275Ab2IFMSo (ORCPT ); Thu, 6 Sep 2012 08:18:44 -0400 Date: Thu, 6 Sep 2012 14:18:42 +0200 From: Michal Hocko To: Glauber Costa Cc: Tejun Heo , linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, linux-mm@kvack.org, Dave Jones , Ben Hutchings , Peter Zijlstra , Paul Turner , Lennart Poettering , Kay Sievers , Kamezawa Hiroyuki , Johannes Weiner Subject: Re: [PATCH v2] memcg: first step towards hierarchical controller Message-ID: <20120906121842.GG22426@dhcp22.suse.cz> References: <20120904143552.GB15683@dhcp22.suse.cz> <50461241.5010300@parallels.com> <20120904145414.GC15683@dhcp22.suse.cz> <50461610.30305@parallels.com> <20120904162501.GE15683@dhcp22.suse.cz> <504709D4.2010800@parallels.com> <20120905144942.GH5388@dhcp22.suse.cz> <20120905201238.GE13737@google.com> <20120906120623.GE22426@dhcp22.suse.cz> <50489270.7060108@parallels.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50489270.7060108@parallels.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 06-09-12 16:09:20, Glauber Costa wrote: > On 09/06/2012 04:06 PM, Michal Hocko wrote: > > On Wed 05-09-12 13:12:38, Tejun Heo wrote: > >> Hello, Michal. > >> > >> On Wed, Sep 05, 2012 at 04:49:42PM +0200, Michal Hocko wrote: > >>> Can we settle on the following 3 steps? > >>> 1) warn about "flat" hierarchies (give it X releases) - I will push it > >>> to as many Suse code streams as possible (hope other distributions > >>> could do the same) > >> > >> I think I'm just gonna trigger WARN from cgroup core if anyone tries > >> to create hierarchy with a controller which doesn't support full > >> hierarchy. WARN_ON_ONCE() at first and then WARN_ON() on each > >> creation later on. > > > > How do you find out that a controller is not fully hierarchical? Memory > > controller can be both. > > > >>> 2) flip the default on the root cgroup & warn when somebody tries to > >>> change it to 0 (give it another X releases) that the knob will be > >>> removed > >>> 3) remove the knob and the whole nonsese > >>> 4) revert 3 if somebody really objects > >> > >> If we can get to 3, I don't think 4 would be a problem. > > > > Agreed. > > > Just so I understand it: > > Michal clearly objected before folding his patch with my Kconfig patch. > But is there still opposition to merge both? I do not find the config option very much useful but if others feel it really is I won't block it. > By having it default-n, only people that are either sure that this is > safe for them, or have more clearly defined lifecycles could set it. -- Michal Hocko SUSE Labs