[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1429289608.3189.47.camel@gmail.com>
Date: Fri, 17 Apr 2015 18:53:28 +0200
From: Mike Galbraith <umgwanakikbuti@...il.com>
To: Michal Schmidt <mschmidt@...hat.com>
Cc: Richard Weinberger <richard.weinberger@...il.com>,
Andy Lutomirski <luto@...capital.net>,
Al Viro <viro@...iv.linux.org.uk>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Arnd Bergmann <arnd@...db.de>,
One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
Tom Gundersen <teg@...m.no>, Jiri Kosina <jkosina@...e.cz>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Daniel Mack <daniel@...que.org>,
David Herrmann <dh.herrmann@...il.com>,
Djalal Harouni <tixxdz@...ndz.org>
Subject: Re: [GIT PULL] kdbus for 4.1-rc1
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@...ervice, and so you could try preventing it from
> starting:
> systemctl mask user@...ervice
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists