On Wed, 2009-07-15 at 19:16 -0400, Ted Baker wrote: > > > 1) The priority of a group seemed to be defined by the priority of > > > the highest-priority thread in the group's run-queue, which means > > > it varies dynamically according to which threads in the group are > > > contending. > > > > > > > This is true, but it also ensures that the time allocated to the group > > is also consumed by group if it wants to. > > I don't see how schedulability analysis can be done with this model, > since a single budget is being expended at varying priorities/deadlines. > Yes, I agree... Right in these days I'm looking at this, and I have some stub code to provide rt groups with a priority the user can, if he wants, set through the cgroupfs. The main problem is dealing with the "distributed" scheduling with push and pull based migration mechanism. Equally interesting, to me, is trying to figure out what kind of analysis (if any!) could be inferred by the current implementation, which could be an hack --as Peter say-- but, has some features I like... Working on it as well, but I progress slowly, I'm not that good at theoretical stuff yet! :-D But that's another thread... I'll let all you know, if interested, soon I hope. :-) 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@xxxxxxxxx / dario.faggioli@xxxxxxxxxx
Attachment:
signature.asc
Description: This is a digitally signed message part
