[lkml]   [2010]   [Jan]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC 10/12][PATCH] SCHED_DEADLINE: group bandwidth management code
On Mon, 2009-12-28 at 15:51 +0100, Peter Zijlstra wrote:
> On Fri, 2009-10-16 at 17:46 +0200, Raistlin wrote:
> > CPU Container Groups support for SCHED_DEADLINE is introduced by this commit.
> >
> > CGroups, if configured, have a SCHED_DEADLINE bandwidth, and it is enforced
> > that the sum of the bandwidths of entities (tasks and groups) belonging to
> > a group stays below its own bandwidth.
> No real comment on the code here, but since we have a deadline bandwidth
> reservation, should we not also couple to the existing rt (fifo)
> bandwidth reservation?
> We can't after all guarantee the FIFO time if there's deadline
> reservations around for more.
Mmm... If I'm getting this right, you're suggesting to decrease from the
available system rt-bandwidth the bandwidth devoted to deadline

This make more than sense to me... I'll think about how to make the code
reflect that.

Thanks and regards,

<<This happens because I choose it to happen!>> (Raistlin Majere)
Dario Faggioli, ReTiS Lab, Scuola Superiore Sant'Anna, Pisa (Italy) / /
[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2010-01-13 10:49    [W:0.191 / U:1.384 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site