Message-ID: <1429289608.3189.47.camel@gmail.com>
Subject: Re: [GIT PULL] kdbus for 4.1-rc1
From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Michal Schmidt <mschmidt@redhat.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
        Andy Lutomirski <luto@amacapital.net>,
        Al Viro <viro@zeniv.linux.org.uk>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        "Eric W. Biederman" <ebiederm@xmission.com>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        Arnd Bergmann <arnd@arndb.de>,
        One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
        Tom Gundersen <teg@jklm.no>, Jiri Kosina <jkosina@suse.cz>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Daniel Mack <daniel@zonque.org>,
        David Herrmann <dh.herrmann@gmail.com>,
        Djalal Harouni <tixxdz@opendz.org>
Date: Fri, 17 Apr 2015 18:53:28 +0200
In-Reply-To: <552E7A3B.3060803@redhat.com>
References: <20150413190350.GA9485@kroah.com>
	 <8738434yjk.fsf@x220.int.ebiederm.org> <20150413194217.GA10837@kroah.com>
	 <20150413202233.GR889@ZenIV.linux.org.uk>
	 <CALCETrUEAxFqwU4beeXYpdyRAO6yDRSNvcBqhvpMVORy00ySgg@mail.gmail.com>
	 <CAFLxGvz9sn7rk1zU5tA8wPtn0T6ujR_tmEhLQeBcVOtKL00wdA@mail.gmail.com>
	 <1429083093.3508.21.camel@gmail.com> <552E7A3B.3060803@redhat.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1408
Lines: 35

On Wed, 2015-04-15 at 16:48 +0200, Michal Schmidt wrote:
> On 04/15/2015 09:31 AM, Mike Galbraith wrote:
> > it seems [systemd] has now mandated group scheduling.
> 
> What makes you think so? Was it the fact that by default you have a
> populated /sys/fs/cgroup/cpu/ hierarchy? This is either because some
> unit requests the use of the cpu controller using one of the CPU*=
> directives from systemd.resource-control(5), or (perhaps more likely)
> because there is a privileged unit with Delegate=yes. The most likely
> candidate is user@0.service, and so you could try preventing it from
> starting:
>   systemctl mask user@0.service

BTW, asking it to symlink it's disabled service to /dev/null, did 
indeed convince it to stop running said disabled service.

> Note that systemd still works without group scheduling or any cgroup
> subsystems enabled in the kernel:
> 
>   $ grep GROUP .config
>   CONFIG_CGROUPS=y

Yup.  CONFIG_CGROUPS=y all by itself isn't useless either, as that 
allows the user to use his box for something other than a doorstop.

Hohum, 'nuff of that ;-)

Thanks for the hint, it seems a tad dainbramaged, but it works.

        -Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/