sched/deadline: Ensure that updates to exclusive cpusets don't break AC
authorJuri Lelli <juri.lelli@arm.com>
Tue, 7 Oct 2014 08:52:11 +0000 (09:52 +0100)
committerIngo Molnar <mingo@kernel.org>
Tue, 28 Oct 2014 09:48:00 +0000 (10:48 +0100)
commitf82f80426f7afcf55953924e71555984a4bd6ce6
tree3a3e15c85f04c11d8f9bc0708b4c8ca439d3431b
parent7f51412a415d87ea8598d14722fb31e4f5701257
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 <juri.lelli@arm.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Li Zefan <lizefan@huawei.com>
Cc: cgroups@vger.kernel.org
Link: http://lkml.kernel.org/r/5433E6AF.5080105@arm.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
include/linux/sched.h
kernel/cpuset.c
kernel/sched/core.c