Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Claudio Scordino <claudio@evidence.eu.com>
To:     linux-kernel@vger.kernel.org
Cc:     peterz@infradead.org, Claudio Scordino <claudio@evidence.eu.com>,
        Luca Abeni <luca.abeni@santannapisa.it>
Subject: [PATCH] sched/deadline: fix runtime accounting in documentation
Date:   Fri, 13 Oct 2017 12:08:06 +0200
Message-Id: <1507889286-24651-1-git-send-email-claudio@evidence.eu.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Signed-off-by: Claudio Scordino <claudio@evidence.eu.com>
Signed-off-by: Luca Abeni <luca.abeni@santannapisa.it>
---
 Documentation/scheduler/sched-deadline.txt | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/Documentation/scheduler/sched-deadline.txt b/Documentation/scheduler/sched-deadline.txt
index e89e36e..79f40c6 100644
--- a/Documentation/scheduler/sched-deadline.txt
+++ b/Documentation/scheduler/sched-deadline.txt
@@ -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
-- 
2.7.4


From 1584614908438516143@xxx Mon Nov 20 19:35:39 +0000 2017
X-GM-THRID: 1584614908438516143
X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread