From: Daniel Bristot de Oliveira <bristot@redhat.com>
To: Ingo Molnar <mingo@redhat.com>, Peter Zijlstra <peterz@infradead.org>
Cc: Xunlei Pang <xpang@redhat.com>, Juri Lelli <juri.lelli@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Luca Abeni <luca.abeni@santannapisa.it>,
Tommaso Cucinotta <tommaso.cucinotta@sssup.it>,
Romulo Silva de Oliveira <romulo.deoliveira@ufsc.br>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] sched/deadline: Use the revised wakeup rule for suspending constrained dl tasks
Date: Mon, 24 Apr 2017 22:43:45 +0200 [thread overview]
Message-ID: <f6d97aba-9b28-fb59-749f-7b9adf276700@redhat.com> (raw)
In-Reply-To: <5c6933890ea6daa3b4edb4983b0c6f094ad3903d.1493045834.git.bristot@redhat.com>
On 04/24/2017 05:18 PM, Daniel Bristot de Oliveira wrote:
> remaining runtime = 4
> laxity = 5
Oops! The laxity is 5... so...
> Knowing the laxity of a task (deadline - t), it is possible to move
> it to the other side of the equality, thus enabling to define max
> remaining runtime a task can use within the absolute deadline, without
> over-running the allowed density:
>
> runtime = (dl_runtime / dl_deadline) * (deadline - t)
>
> For instance, in our previous example, the task could still run:
>
> runtime = ( 5 / 7 ) * 4
> runtime = 2.85 ms
This should be:
runtime = ( 5 / 7 ) * 5
runtime = 3.57 ms
even better :-)
-- Daniel
next prev parent reply other threads:[~2017-04-24 20:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 15:18 Daniel Bristot de Oliveira
2017-04-24 17:00 ` Steven Rostedt
2017-04-24 18:51 ` Daniel Bristot de Oliveira
2017-04-24 20:43 ` Daniel Bristot de Oliveira [this message]
2017-05-04 14:17 ` Peter Zijlstra
2017-05-04 14:23 ` Peter Zijlstra
2017-05-11 17:07 ` Daniel Bristot de Oliveira
2017-05-04 14:26 ` Peter Zijlstra
2017-05-11 17:08 ` Daniel Bristot de Oliveira
2017-05-11 17:03 ` Daniel Bristot de Oliveira
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=f6d97aba-9b28-fb59-749f-7b9adf276700@redhat.com \
--to=bristot@redhat.com \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@santannapisa.it \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=romulo.deoliveira@ufsc.br \
--cc=rostedt@goodmis.org \
--cc=tommaso.cucinotta@sssup.it \
--cc=xpang@redhat.com \
/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
all inboxes | Powered by JetHome®