The list of open points and issues for this work: - review/testing
- handle the PI case better The only thing I can come up with currently is to basically have two priority arrays one for boosted and one for non boosted tasks, and normally run the highest of either array, but in the case of a throttled group, only pick from the boosted array. Not sure I like that for its space overhead, Steven? - I occasionally see a weird lockup on iterating the task_groups list on smp machines. - I failed to see anything wrong, but hey, this stack of used brown paper bags is steadily growing. - figure out what to do for UID based group scheduling, the current implementation leaves it impossible for !root users to execute real time tasks by setting rt_runtime_us to 0, and it has no way to change it. Srivatsa, what happened to the per uid weight patches?, Perhaps we can extend that interface to allow changing this. - I guess documentation needs to be written ;-)
signature.asc
Description: This is a digitally signed message part
