lkml.org 
[lkml]   [2010]   [Jan]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [RFC 9/12][PATCH] SCHED_DEADLINE: system wide bandwidth management
From
Date
On Mon, 2009-12-28 at 15:44 +0100, Peter Zijlstra wrote:
> > Default value is _zero_ bandwidth available, thus write some numbers in those
> > files before trying to start some SCHED_DEADLINE task. Setting runtime > period
> > is allowed (i.e., more than 100% bandwidth available for -deadline tasks),
> > since it makes more than sense in SMP systems.
>
> Right, so the current rt bandwidth controls go up to 100%, where 100% is
> root_domain wide. That is, the bandwidth usage scale is irrespective of
> the number of cpus.
>
Yep, I know. Mine controls were working a little bit different because
of the fact I have bandwidth control at the task group --not rq-- level.
Anyway...

> If that was the best choice could of course be argued, but since we have
> that, it would be strange to add another set of controls which do not
> conform.
>
... I again agree that consistency come first, and I'll move the
controls in the right place, and convert them to the conforming
behavior.

Thanks and regards,
Dario

--
<<This happens because I choose it to happen!>> (Raistlin Majere)
----------------------------------------------------------------------
Dario Faggioli, ReTiS Lab, Scuola Superiore Sant'Anna, Pisa (Italy)

http://blog.linux.it/raistlin / raistlin@ekiga.net /
dario.faggioli@jabber.org
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2010-01-13 10:43    [W:4.203 / U:0.272 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site