Skip to contentSkip to conversation

sched/deadline: fix runtime accounting in documentation

PATCH Superseded Claudio Scordino 2 participants 2 messages Oct 13, 2017 – Nov 13, 2017 Documentation

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 sched/deadline: fix runtime accounting in documentation

---
 Documentation/scheduler/sched-deadline.txt | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)
Documentation/scheduler/sched-deadline.txt +9 -3
index e89e36e..79f40c6 100644
@@ -204,10 +204,16 @@ CONTENTS
  It does so by decrementing the runtime of the executing task Ti at a pace equal
  to
 
-           dq = -max{ Ui, (1 - Uinact) } dt
+           dq = -max{ Ui / Umax, (1 - Uinact - Uextra) } dt
 
- where Uinact is the inactive utilization, computed as (this_bq - running_bw),
- and Ui is the bandwidth of task Ti.
+ where:
+
+  - Ui is the bandwidth of task Ti;
+  - Umax is the maximum reclaimable utilization (subject to RT limits);
+  - Uinact is the (per runqueue) inactive utilization, computed as
+    (this_bq - running_bw);
+  - Uextra is the (per runqueue) extra reclaimable utilization
+    (subject to RT limits).
 
 
  Let's now see a trivial example of two deadline tasks with runtime equal
Signature · 1 line
2.7.4
Acked-by on v1 1/1
#1 lore raw
Quoted 12 lines · Claudio Scordino
---
 Documentation/scheduler/sched-deadline.txt | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)
Documentation/scheduler/sched-deadline.txt +0 -0
index e89e36e..79f40c6 100644
@@ -204,10 +204,16 @@ CONTENTS
  It does so by decrementing the runtime of the executing task Ti at a pace equal

Documentation/scheduler/sched-deadline.txt CONTENTS · line 211

Quoted 10 lines
Documentation/scheduler/sched-deadline.txt +4 -3
  to
 
-           dq = -max{ Ui, (1 - Uinact) } dt
+           dq = -max{ Ui / Umax, (1 - Uinact - Uextra) } dt
 
- where Uinact is the inactive utilization, computed as (this_bq - running_bw),
- and Ui is the bandwidth of task Ti.
+ where:
+
+  - Ui is the bandwidth of task Ti;

Just one very very small addition to make it more clear:

Documentation/scheduler/sched-deadline.txt CONTENTS · line 212

Quoted 1 line
Documentation/scheduler/sched-deadline.txt +1 -0
+  - Umax is the maximum reclaimable utilization (subject to RT limits);

^^^^^^^^^^^^^^^^^^^
(subjected to RT Throttling limits)

Anyways,

Quoted 8 lines
Documentation/scheduler/sched-deadline.txt +4 -0
+  - Uinact is the (per runqueue) inactive utilization, computed as
+    (this_bq - running_bw);
+  - Uextra is the (per runqueue) extra reclaimable utilization
+    (subject to RT limits).
 
 
  Let's now see a trivial example of two deadline tasks with runtime equal