summaryrefslogtreecommitdiff
path: root/Documentation/scheduler
diff options
context:
space:
mode:
authorSuchit Karunakaran <suchitkarunakaran@gmail.com>2025-02-19 16:52:54 +0530
committerJonathan Corbet <corbet@lwn.net>2025-02-21 13:27:05 -0700
commit999fd62b066030959337b5fed5b80d5eb12de2a2 (patch)
tree734146d2d3af400bf390ad839a9bfa72ac805f1c /Documentation/scheduler
parent757b9d0a4fd2eda3f4d883ef8ac6998d73004df7 (diff)
docs: scheduler: fix spelling in sched-bwc documentation
Fix spelling of "interference" in the CFS bandwidth control documentation. The word was misspelled as "interferenece". Signed-off-by: Suchit Karunakaran <suchitkarunakaran@gmail.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net> Link: https://lore.kernel.org/r/20250219112254.28691-1-suchitkarunakaran@gmail.com
Diffstat (limited to 'Documentation/scheduler')
-rw-r--r--Documentation/scheduler/sched-bwc.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/scheduler/sched-bwc.rst b/Documentation/scheduler/sched-bwc.rst
index 41ed2ceafc92..e881a945c188 100644
--- a/Documentation/scheduler/sched-bwc.rst
+++ b/Documentation/scheduler/sched-bwc.rst
@@ -59,7 +59,7 @@ At the same time, we can say that the worst case deadline miss, will be
\Sum e_i; that is, there is a bounded tardiness (under the assumption
that x+e is indeed WCET).
-The interferenece when using burst is valued by the possibilities for
+The interference when using burst is valued by the possibilities for
missing the deadline and the average WCET. Test results showed that when
there many cgroups or CPU is under utilized, the interference is
limited. More details are shown in: