[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4CE5C66F.3050300@zytor.com>
Date: Thu, 18 Nov 2010 16:35:59 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Lennart Poettering <mzxreary@...inter.de>
CC: Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Dhaval Giani <dhaval.giani@...il.com>,
Mike Galbraith <efault@....de>,
Vivek Goyal <vgoyal@...hat.com>,
Oleg Nesterov <oleg@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Markus Trippelsdorf <markus@...ppelsdorf.de>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Ingo Molnar <mingo@...e.hu>,
LKML <linux-kernel@...r.kernel.org>,
Balbir Singh <balbir@...ux.vnet.ibm.com>
Subject: Re: [RFC/RFT PATCH v3] sched: automated per tty task groups
On 11/16/2010 12:05 PM, Lennart Poettering wrote:
> On Tue, 16.11.10 19:08, Peter Zijlstra (a.p.zijlstra@...llo.nl) wrote:
>
>>
>> On Tue, 2010-11-16 at 18:03 +0100, Lennart Poettering wrote:
>>> Binding something like this to TTYs is just backwards. No graphical
>>> session has a TTY attached anymore. And there might be multiple TTYs
>>> used in the same session.
>>
>> Using a group per tty makes sense for us console jockeys..
>
> Well, then maybe you shouldn't claim this was relevant for anybody but
> yourself. Because it is irrelevant for most users if it is bound to the TTY.
>
For what it's worth, I suspect that the object that should be bound to
is probably not the tty, but rather the session ID of the process (which
generally is 1:1 with controlling TTY for console processes.)
-hpa
--
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