[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1290129157.18039.70.camel@maggy.simson.net>
Date: Thu, 18 Nov 2010 18:12:37 -0700
From: Mike Galbraith <efault@....de>
To: Samuel Thibault <samuel.thibault@...-lyon.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Hans-Peter Jansen <hpj@...la.net>,
linux-kernel@...r.kernel.org,
Lennart Poettering <mzxreary@...inter.de>, 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 Fri, 2010-11-19 at 01:59 +0100, Samuel Thibault wrote:
> Linus Torvalds, le Thu 18 Nov 2010 16:42:27 -0800, a écrit :
> > Once per session is about as much as is acceptable. That's the kind of
> > granularity we should look at. So things like "groups per user",
> > "groups per session", "groups per one graphical application" are good.
> > Not things that can happen tens of thousands of times a second.
>
> All right. I believe that should already work quite well both for
> desktop and servers indeed. "Per one graphical application" will most
> probably require desktop panel patching, however.
I think that could be done with a fork flag with the same semantics as
reset on fork. Once your task launcher (ala kdeinit) is tagged, it
launches task groups, the children lose that ability. That requires
userspace interaction though, dunno how you'd detect automatically.
-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