From: Daniel Bristot de Oliveira <bristot@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>, 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: Thu, 11 May 2017 19:07:01 +0200 [thread overview]
Message-ID: <9eb70e53-0d8a-94e8-7da4-b577aaafd56e@redhat.com> (raw)
In-Reply-To: <20170504142329.wanerqq5nsmu3blr@hirez.programming.kicks-ass.net>
On 05/04/2017 04:23 PM, Peter Zijlstra wrote:
> On Thu, May 04, 2017 at 04:17:21PM +0200, Peter Zijlstra wrote:
>> On Mon, Apr 24, 2017 at 05:18:35PM +0200, Daniel Bristot de Oliveira wrote:
>>> +static void
>>> +update_dl_revised_wakeup(struct sched_dl_entity *dl_se, struct rq *rq)
>>> +{
>>> + u64 density = div64_u64(dl_se->dl_runtime << 20, dl_se->dl_deadline);
>>> + u64 laxity = dl_se->deadline - rq_clock(rq);
>>> +
>>> + BUG_ON(laxity < 0);
>> Compiler will make that go away, by virtue of laxity being unsigned.
> Also, so we want that to BUG (or even WARN) in a soft RT setting.
> Remember, GEDF does not guarantee we make our deadlines.
The point is that, a task with laxity < 0 should be throttled before
this point by:
df8eac8cafce ("sched/deadline: Throttle a constrained deadline task
activated after the deadline")
Arrive here with (laxity < 0) meas that we skipped that check.
>> We use two difference CBS rules:
> _different_, clearly I cannot type anymore either ;-)
ops... :-)
-- Daniel
next prev parent reply other threads:[~2017-05-11 17:07 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
2017-05-04 14:17 ` Peter Zijlstra
2017-05-04 14:23 ` Peter Zijlstra
2017-05-11 17:07 ` Daniel Bristot de Oliveira [this message]
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=9eb70e53-0d8a-94e8-7da4-b577aaafd56e@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®