diff options
author | Dietmar Eggemann <[email protected]> | 2022-03-02 19:34:30 +0100 |
---|---|---|
committer | Peter Zijlstra <[email protected]> | 2022-03-08 16:08:39 +0100 |
commit | 772b6539fdda31462cc08368e78df60b31a58bab (patch) | |
tree | 3c7a704344601c626a28aa7b2e76e30abcb7dbb7 /lib/test_fortify/write_overflow-strlcpy-src.c | |
parent | f1304ecbef3c9f4aec119ce2a07335d3a0bc55a6 (diff) |
sched/deadline: Merge dl_task_can_attach() and dl_cpu_busy()
Both functions are doing almost the same, that is checking if admission
control is still respected.
With exclusive cpusets, dl_task_can_attach() checks if the destination
cpuset (i.e. its root domain) has enough CPU capacity to accommodate the
task.
dl_cpu_busy() checks if there is enough CPU capacity in the cpuset in
case the CPU is hot-plugged out.
dl_task_can_attach() is used to check if a task can be admitted while
dl_cpu_busy() is used to check if a CPU can be hotplugged out.
Make dl_cpu_busy() able to deal with a task and use it instead of
dl_task_can_attach() in task_can_attach().
Signed-off-by: Dietmar Eggemann <[email protected]>
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Acked-by: Juri Lelli <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'lib/test_fortify/write_overflow-strlcpy-src.c')
0 files changed, 0 insertions, 0 deletions