[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101117002159.GA3184@tango.0pointer.de>
Date: Wed, 17 Nov 2010 01:21:59 +0100
From: Lennart Poettering <mzxreary@...inter.de>
To: Ted Ts'o <tytso@....edu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Dhaval Giani <dhaval.giani@...il.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Mike Galbraith <efault@....de>,
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>,
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 Tue, 16.11.10 18:39, Ted Ts'o (tytso@....edu) wrote:
>
> On Tue, Nov 16, 2010 at 10:19:09PM +0100, Lennart Poettering wrote:
> > Well, my plan was actually to by default put everything into its own
> > group, and then let users opt-out of that for specific processes, if the
> > want to.
>
> How many users are likely to do this, though?
>
> I think you really want to make this be something which the
> application can specify by default that they should start in their own
> cgroup. One idea might be to it to the applications menu entry:
>
> http://standards.freedesktop.org/desktop-entry-spec/latest/
>
> ... so there would be a new key value pair, "start_in_cgroup", that
> would allow the user to start an application in their own cgroup. It
> would be up to the desktop launcher to honor that if it was present.
This is pretty much in line with what I want to do, except I want
opt-out, not opt-in behaviour here.
Lennart
--
Lennart Poettering - Red Hat, Inc.
--
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