Skip to content

Commit bbf5254

Browse files
WerkovJonathan Corbet
authored andcommitted
Documentation: sched/RT: Update paragraphs about RT bandwidth control
This has slightly changed with the introduction of fair_server. Update the most relevant parts. Link: https://lore.kernel.org/r/[email protected]/ Signed-off-by: Michal Koutný <[email protected]> Reviewed-by: Juri Lelli <[email protected]> Acked-by: Juri Lelli <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]> Link: https://lore.kernel.org/r/[email protected]
1 parent 80568f4 commit bbf5254

File tree

2 files changed

+11
-10
lines changed

2 files changed

+11
-10
lines changed

Documentation/scheduler/sched-deadline.rst

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -591,12 +591,13 @@ Deadline Task Scheduling
591591

592592
The system wide settings are configured under the /proc virtual file system.
593593

594-
For now the -rt knobs are used for -deadline admission control and the
595-
-deadline runtime is accounted against the -rt runtime. We realize that this
596-
isn't entirely desirable; however, it is better to have a small interface for
597-
now, and be able to change it easily later. The ideal situation (see 5.) is to
598-
run -rt tasks from a -deadline server; in which case the -rt bandwidth is a
599-
direct subset of dl_bw.
594+
For now the -rt knobs are used for -deadline admission control and with
595+
CONFIG_RT_GROUP_SCHED the -deadline runtime is accounted against the (root)
596+
-rt runtime. With !CONFIG_RT_GROUP_SCHED the knob only serves for the -dl
597+
admission control. We realize that this isn't entirely desirable; however, it
598+
is better to have a small interface for now, and be able to change it easily
599+
later. The ideal situation (see 5.) is to run -rt tasks from a -deadline
600+
server; in which case the -rt bandwidth is a direct subset of dl_bw.
600601

601602
This means that, for a root_domain comprising M CPUs, -deadline tasks
602603
can be created while the sum of their bandwidths stays below:

Documentation/scheduler/sched-rt-group.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -92,10 +92,10 @@ The system wide settings are configured under the /proc virtual file system:
9292
/proc/sys/kernel/sched_rt_runtime_us:
9393
A global limit on how much time real-time scheduling may use. This is always
9494
less or equal to the period_us, as it denotes the time allocated from the
95-
period_us for the real-time tasks. Even without CONFIG_RT_GROUP_SCHED enabled,
96-
this will limit time reserved to real-time processes. With
97-
CONFIG_RT_GROUP_SCHED=y it signifies the total bandwidth available to all
98-
real-time groups.
95+
period_us for the real-time tasks. Without CONFIG_RT_GROUP_SCHED enabled,
96+
this only serves for admission control of deadline tasks. With
97+
CONFIG_RT_GROUP_SCHED=y it also signifies the total bandwidth available to
98+
all real-time groups.
9999

100100
* Time is specified in us because the interface is s32. This gives an
101101
operating range from 1us to about 35 minutes.

0 commit comments

Comments
 (0)