From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755293Ab0EMVT0 (ORCPT ); Thu, 13 May 2010 17:19:26 -0400 Received: from bombadil.infradead.org ([18.85.46.34]:46510 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752508Ab0EMVTY convert rfc822-to-8bit (ORCPT ); Thu, 13 May 2010 17:19:24 -0400 Subject: Re: [PATCH/RFC] Have sane default values for cpusets From: Peter Zijlstra To: Lennart Poettering Cc: Dhaval Giani , James Kosin , linux-kernel@vger.kernel.org, menage@google.com, balbir@linux.vnet.ibm.com, jsafrane@redhat.com, tglx@linutronix.de In-Reply-To: <20100513140354.GA12639@tango.0pointer.de> References: <4BEAB6FC.8090105@intcomgrp.com> <1273674048.1626.117.camel@laptop> <20100512190757.GA421@tango.0pointer.de> <1273755719.5605.3537.camel@twins> <20100513140354.GA12639@tango.0pointer.de> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Date: Thu, 13 May 2010 23:19:06 +0200 Message-ID: <1273785546.5605.3556.camel@twins> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2010-05-13 at 16:03 +0200, Lennart Poettering wrote: > > On Wed, 2010-05-12 at 21:07 +0200, Lennart Poettering wrote: > > > See Dhaval's patch on the background of systemd > > > (http://0pointer.de/blog/projects/systemd.html). When a service is > > > started in systemd, we create a cgroup for it, when it ends, we remove > > > it. > > > > I seriously hope that's optional, because I for one would really hate a > > system that does that. I still mostly build kernels with only cpuset in > > and really don't want anybody but me creating groups in there. > > By default systemd will create its groups in the "debug" hierarchy, (at > least for now, in the long run i'd like to see "noop" hierarchy or so, > that doesn't sound so temporary), since that controller is not useful > for anything but keeping track of processes. So it shouldn't bother you > at all. Will it still work with a CONFIG_CGROUP=n kernel? I see distributions deteriorate, you cannot even boot a raw bzImage kernel without initrd on most distros (sure, its not too hard to fix, but still). Also, I get all kinds of dumb-ass init-script failures for not having modules but stuff built-in. A prime example is NFS failing on start on both fedora and ubuntu with a built-in nfs server (for different but both retarded reasons). Requiring CONFIG_CGROUP=y to even get init running seems like a final straw to ensure nobody will ever get anything to boot these days.