sched/core: Disable CONFIG_SCHED_CORE by default
This option at minimum adds extra code to the scheduler - even if it's default unused - and most users wouldn't want it. Reported-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Ingo Molnar <mingo@kernel.org>
This commit is contained in:
parent
adf3c31e18
commit
d2343cb8d1
1 changed files with 3 additions and 3 deletions
|
@ -102,7 +102,6 @@ config PREEMPT_DYNAMIC
|
||||||
|
|
||||||
config SCHED_CORE
|
config SCHED_CORE
|
||||||
bool "Core Scheduling for SMT"
|
bool "Core Scheduling for SMT"
|
||||||
default y
|
|
||||||
depends on SCHED_SMT
|
depends on SCHED_SMT
|
||||||
help
|
help
|
||||||
This option permits Core Scheduling, a means of coordinated task
|
This option permits Core Scheduling, a means of coordinated task
|
||||||
|
@ -115,7 +114,8 @@ config SCHED_CORE
|
||||||
- mitigation of some (not all) SMT side channels;
|
- mitigation of some (not all) SMT side channels;
|
||||||
- limiting SMT interference to improve determinism and/or performance.
|
- limiting SMT interference to improve determinism and/or performance.
|
||||||
|
|
||||||
SCHED_CORE is default enabled when SCHED_SMT is enabled -- when
|
SCHED_CORE is default disabled. When it is enabled and unused,
|
||||||
unused there should be no impact on performance.
|
which is the likely usage by Linux distributions, there should
|
||||||
|
be no measurable impact on performance.
|
||||||
|
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue