[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1337942569.9783.183.camel@laptop>
Date: Fri, 25 May 2012 12:42:49 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Juri Lelli <juri.lelli@...il.com>
Cc: tglx@...utronix.de, mingo@...hat.com, rostedt@...dmis.org,
oleg@...hat.com, fweisbec@...il.com, darren@...art.com,
johan.eker@...csson.com, p.faure@...tech.ch,
linux-kernel@...r.kernel.org, claudio@...dence.eu.com,
michael@...rulasolutions.com, fchecconi@...il.com,
tommaso.cucinotta@...up.it, nicola.manica@...i.unitn.it,
luca.abeni@...tn.it, dhaval.giani@...il.com, hgu1972@...il.com,
paulmck@...ux.vnet.ibm.com, raistlin@...ux.it,
insop.song@...csson.com, liming.wang@...driver.com,
jkacur@...hat.com, harald.gustafsson@...csson.com
Subject: Re: [RFC][PATCH 00/15] sched: SCHED_DEADLINE v5
On Wed, 2012-05-23 at 23:42 +0200, Juri Lelli wrote:
> Still missing/incomplete:
> - (c)group based bandwidth management, and maybe scheduling;
The b/w stuff for cgroups shouldn't be particularly hard, right? It
shouldn't be more than ensuring the utilization sum of all children
stays below the set value.
Or am I missing something?
> - bandwidth inheritance (to replace deadline/priority inheritance);
Yes please, but this is somewhat longer term, I think the band-aids in
place are sufficient to allow us to move fwd.
> - access control for non-root users (and related security concerns to
> address).
Right, so could you detail what all is needed to allow regular users to
create dl tasks?
Aside from this, Ingo, Thomas, Steven do you agree in merging these
patches as a suitable base to continue work from?
--
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