Skip to content

Commit b136f68

Browse files
committed
Merge tag 'sched-urgent-2024-03-24' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull scheduler doc clarification from Thomas Gleixner: "A single update for the documentation of the base_slice_ns tunable to clarify that any value which is less than the tick slice has no effect because the scheduler tick is not guaranteed to happen within the set time slice" * tag 'sched-urgent-2024-03-24' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: sched/doc: Update documentation for base_slice_ns and CONFIG_HZ relation
2 parents 864ad04 + a269793 commit b136f68

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

Documentation/scheduler/sched-design-CFS.rst

+3
Original file line numberDiff line numberDiff line change
@@ -100,6 +100,9 @@ which can be used to tune the scheduler from "desktop" (i.e., low latencies) to
100100
"server" (i.e., good batching) workloads. It defaults to a setting suitable
101101
for desktop workloads. SCHED_BATCH is handled by the CFS scheduler module too.
102102

103+
In case CONFIG_HZ results in base_slice_ns < TICK_NSEC, the value of
104+
base_slice_ns will have little to no impact on the workloads.
105+
103106
Due to its design, the CFS scheduler is not prone to any of the "attacks" that
104107
exist today against the heuristics of the stock scheduler: fiftyp.c, thud.c,
105108
chew.c, ring-test.c, massive_intr.c all work fine and do not impact

0 commit comments

Comments
 (0)