[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1429112077.3355.22.camel@gmail.com>
Date: Wed, 15 Apr 2015 17:34:37 +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?
If group sched is available, systemd decides on its own to use it,
thus making the decision to eat that overhead for me should I happen
to boot say an enterprise kernel to do some performance measurements.
Perhaps there is a way to beg it to please not do that, but if so, I
didn't find it in time. The service that started group scheduling was
explicitly disabled by me, but systemd started it at boot despite
that. Perhaps I didn't express my wishes clearly enough, or I need to
burn a virgin or something to become worthy of its attention, dunno.
Applying my axe to its tentacles fixed the communication issue.
-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