diff options
| author | Peter Zijlstra <a.p.zijlstra@chello.nl> | 2008-02-13 15:45:39 +0100 |
|---|---|---|
| committer | Ingo Molnar <mingo@elte.hu> | 2008-02-13 15:45:39 +0100 |
| commit | 23b0fdfc9299b137bd126e9dc22f62a59dae546d (patch) | |
| tree | 22019172c555109b69a73da76561d99d7776c4f7 /Documentation/cpu-load.txt | |
| parent | sched: fix incorrect irq lock usage in normalize_rt_tasks() (diff) | |
| download | linux-23b0fdfc9299b137bd126e9dc22f62a59dae546d.tar.xz linux-23b0fdfc9299b137bd126e9dc22f62a59dae546d.zip | |
sched: rt-group: deal with PI
Steven mentioned the fun case where a lock holding task will be throttled.
Simple fix: allow groups that have boosted tasks to run anyway.
If a runnable task in a throttled group gets boosted the dequeue/enqueue
done by rt_mutex_setprio() is enough to unthrottle the group.
This is ofcourse not quite correct. Two possible ways forward are:
- second prio array for boosted tasks
- boost to a prio ceiling (this would also work for deadline scheduling)
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'Documentation/cpu-load.txt')
0 files changed, 0 insertions, 0 deletions