[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1290122978.18039.46.camel@maggy.simson.net>
Date: Thu, 18 Nov 2010 16:29:38 -0700
From: Mike Galbraith <efault@....de>
To: Hans-Peter Jansen <hpj@...la.net>
Cc: linux-kernel@...r.kernel.org,
Lennart Poettering <mzxreary@...inter.de>,
Linus Torvalds <torvalds@...ux-foundation.org>, david@...g.hm,
Dhaval Giani <dhaval.giani@...il.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Vivek Goyal <vgoyal@...hat.com>,
Oleg Nesterov <oleg@...hat.com>,
Markus Trippelsdorf <markus@...ppelsdorf.de>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Ingo Molnar <mingo@...e.hu>,
Balbir Singh <balbir@...ux.vnet.ibm.com>
Subject: Re: [RFC/RFT PATCH v3] sched: automated per tty task groups
On Thu, 2010-11-18 at 23:33 +0100, Hans-Peter Jansen wrote:
> If you think, that systemd can solve this and probably other aspects of
> responsiveness, go for it, compete with it, and _prove_ it with real
> facts and numbers, not just hand waving.
Of course systemd can do it. You don't even need systemd, autogroup or
whatever else if you don't mind a little scripting. There's nothing to
prove, any numbers he generates will be identical with any numbers I
generate... it's the same scheduler whether you configure it from
userspace or kernelspace.
> As already mentioned countless times (and some of it was even renamed
> for this very fact): the grouping by tty is just a starter. There are
Actually, I switched to setsid alone for now at least, and the only
thing in the root group is kernel threads.
-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