From: tip-bot for Claudio Scordino <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: hpa@zytor.com, corbet@lwn.net, linux-kernel@vger.kernel.org,
mingo@kernel.org, peterz@infradead.org,
mathieu.poirier@linaro.org, torvalds@linux-foundation.org,
claudio@evidence.eu.com, tommaso.cucinotta@sssup.it,
tglx@linutronix.de, luca.abeni@santannapisa.it,
bristot@redhat.com
Subject: [tip:sched/urgent] sched/deadline: Fix the description of runtime accounting in the documentation
Date: Thu, 16 Nov 2017 07:52:15 -0800 [thread overview]
Message-ID: <tip-5c0342ca7ef17220d8dd2da68d0d349c26ab19df@git.kernel.org> (raw)
In-Reply-To: <1510658366-28995-1-git-send-email-claudio@evidence.eu.com>
Commit-ID: 5c0342ca7ef17220d8dd2da68d0d349c26ab19df
Gitweb: https://git.kernel.org/tip/5c0342ca7ef17220d8dd2da68d0d349c26ab19df
Author: Claudio Scordino <claudio@evidence.eu.com>
AuthorDate: Tue, 14 Nov 2017 12:19:26 +0100
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Thu, 16 Nov 2017 09:00:35 +0100
sched/deadline: Fix the description of runtime accounting in the documentation
Signed-off-by: Claudio Scordino <claudio@evidence.eu.com>
Signed-off-by: Luca Abeni <luca.abeni@santannapisa.it>
Acked-by: Daniel Bristot de Oliveira <bristot@redhat.com>
Acked-by: Peter Zijlstra <peterz@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Tommaso Cucinotta <tommaso.cucinotta@sssup.it>
Cc: linux-doc@vger.kernel.org
Link: http://lkml.kernel.org/r/1510658366-28995-1-git-send-email-claudio@evidence.eu.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
Documentation/scheduler/sched-deadline.txt | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/Documentation/scheduler/sched-deadline.txt b/Documentation/scheduler/sched-deadline.txt
index e89e36e..8ce78f8 100644
--- a/Documentation/scheduler/sched-deadline.txt
+++ b/Documentation/scheduler/sched-deadline.txt
@@ -204,10 +204,17 @@ 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 (subjected to RT throttling
+ limits);
+ - Uinact is the (per runqueue) inactive utilization, computed as
+ (this_bq - running_bw);
+ - Uextra is the (per runqueue) extra reclaimable utilization
+ (subjected to RT throttling limits).
Let's now see a trivial example of two deadline tasks with runtime equal
prev parent reply other threads:[~2017-11-16 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 11:19 [PATCH v2] sched/deadline: fix runtime accounting in documentation Claudio Scordino
2017-11-14 18:41 ` Mathieu Poirier
2017-11-15 10:34 ` Peter Zijlstra
2017-11-16 8:00 ` Ingo Molnar
2017-11-16 15:52 ` tip-bot for Claudio Scordino [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tip-5c0342ca7ef17220d8dd2da68d0d349c26ab19df@git.kernel.org \
--to=tipbot@zytor.com \
--cc=bristot@redhat.com \
--cc=claudio@evidence.eu.com \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luca.abeni@santannapisa.it \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tommaso.cucinotta@sssup.it \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox