diff options
| author | Juri Lelli <[email protected]> | 2014-10-07 09:52:11 +0100 |
|---|---|---|
| committer | Ingo Molnar <[email protected]> | 2014-10-28 10:48:00 +0100 |
| commit | f82f80426f7afcf55953924e71555984a4bd6ce6 (patch) | |
| tree | 3a3e15c85f04c11d8f9bc0708b4c8ca439d3431b /tools/perf/scripts/python | |
| parent | 7f51412a415d87ea8598d14722fb31e4f5701257 (diff) | |
sched/deadline: Ensure that updates to exclusive cpusets don't break AC
How we deal with updates to exclusive cpusets is currently broken.
As an example, suppose we have an exclusive cpuset composed of
two cpus: A[cpu0,cpu1]. We can assign SCHED_DEADLINE task to it
up to the allowed bandwidth. If we want now to modify cpusetA's
cpumask, we have to check that removing a cpu's amount of
bandwidth doesn't break AC guarantees. This thing isn't checked
in the current code.
This patch fixes the problem above, denying an update if the
new cpumask won't have enough bandwidth for SCHED_DEADLINE tasks
that are currently active.
Signed-off-by: Juri Lelli <[email protected]>
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Li Zefan <[email protected]>
Cc: [email protected]
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions