diff options
author | Valentin Schneider <valentin.schneider@arm.com> | 2020-04-15 23:05:06 +0200 |
---|---|---|
committer | Peter Zijlstra <peterz@infradead.org> | 2020-04-30 20:14:39 +0200 |
commit | e669ac8ab952df2f07dee1e1efbf40647d6de332 (patch) | |
tree | 19a14e3cb10525a7552d77d4927d531fe2d86dd3 /ipc/namespace.c | |
parent | sched/debug: Make sd->flags sysctl read-only (diff) | |
download | linux-e669ac8ab952df2f07dee1e1efbf40647d6de332.tar.xz linux-e669ac8ab952df2f07dee1e1efbf40647d6de332.zip |
sched: Remove checks against SD_LOAD_BALANCE
The SD_LOAD_BALANCE flag is set unconditionally for all domains in
sd_init(). By making the sched_domain->flags syctl interface read-only, we
have removed the last piece of code that could clear that flag - as such,
it will now be always present. Rather than to keep carrying it along, we
can work towards getting rid of it entirely.
cpusets don't need it because they can make CPUs be attached to the NULL
domain (e.g. cpuset with sched_load_balance=0), or to a partitioned
root_domain, i.e. a sched_domain hierarchy that doesn't span the entire
system (e.g. root cpuset with sched_load_balance=0 and sibling cpusets with
sched_load_balance=1).
isolcpus apply the same "trick": isolated CPUs are explicitly taken out of
the sched_domain rebuild (using housekeeping_cpumask()), so they get the
NULL domain treatment as well.
Remove the checks against SD_LOAD_BALANCE.
Signed-off-by: Valentin Schneider <valentin.schneider@arm.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lkml.kernel.org/r/20200415210512.805-4-valentin.schneider@arm.com
Diffstat (limited to 'ipc/namespace.c')
0 files changed, 0 insertions, 0 deletions