[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1267273991.22519.744.camel@laptop>
Date: Sat, 27 Feb 2010 13:33:11 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Fabio Checconi <fchecconi@...il.com>
Cc: Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
Paul Turner <pjt@...gle.com>,
Dario Faggioli <faggioli@...dalf.sssup.it>,
Michael Trimarchi <michael@...dence.eu.com>,
Dhaval Giani <dhaval@...is.sssup.it>,
Tommaso Cucinotta <t.cucinotta@...up.it>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] sched: use EDF to throttle RT task groups v2
On Tue, 2010-02-23 at 19:56 +0100, Fabio Checconi wrote:
> - Since it is not easy to mix tasks and groups on the same scheduler
> queue (tasks have no deadlines), the bandwidth reserved to the tasks
> in a group is controlled with two additional cgroup attributes:
> rt_task_runtime_us and rt_task_period_us. These attributes control,
> within a cgroup, how much bandwidth is reserved to the tasks it
> contains. The old attributes, rt_runtime_us and rt_period_us, are
> still there, and control the bandwidth assigned to the cgroup. They
> are used only for admission control.
We could do this implicitly by simply setting the task_bandwidth to the
cgroup bandwidth - \Sum_children bandwidth.
Having it explicit gives the administrator slightly more control at the
cost of a more complex interface.
Just wondering if you thought about this trade-off?
--
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