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:08:22 +0200 [thread overview]
Message-ID: <94f331e7-913e-04c8-c065-765d39c851f7@redhat.com> (raw)
In-Reply-To: <20170504142632.fdnwfqxcas7d3t7x@hirez.programming.kicks-ass.net>
On 05/04/2017 04:26 PM, Peter Zijlstra wrote:
> On Thu, May 04, 2017 at 04:17:21PM +0200, Peter Zijlstra wrote:
>> We use two difference CBS rules:
>>
>> 1) the original CBS rule for implicit deadline tasks;
>> 2) the revised CBS rule for constrained deadline tasks.
>>> @@ -500,6 +550,14 @@ static void update_dl_entity(struct sched_dl_entity *dl_se,
>>>
>>> if (dl_time_before(dl_se->deadline, rq_clock(rq)) ||
>>> dl_entity_overflow(dl_se, pi_se, rq_clock(rq))) {
>>> +
>>> + if (unlikely(dl_is_constrained(dl_se) &&
>>> + !dl_time_before(dl_se->deadline, rq_clock(rq)) &&
>>> + !dl_se->dl_boosted)){
>>> + update_dl_revised_wakeup(dl_se, rq);
>>> + return;
>>> + }
>>> +
>>> dl_se->deadline = rq_clock(rq) + pi_se->dl_deadline;
>>> dl_se->runtime = pi_se->dl_runtime;
>>> }
> That comment above does not match the code. We can still use the
> original CBS rule for constrained tasks.
>
> We only use the revised CBS rule when the constrained task hasn't missed
> its deadline yet.
Correct. I will improve the explanation.
Thank you very much for all comments :-)
-- Daniel
next prev parent reply other threads:[~2017-05-11 17:08 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
2017-05-04 14:26 ` Peter Zijlstra
2017-05-11 17:08 ` Daniel Bristot de Oliveira [this message]
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=94f331e7-913e-04c8-c065-765d39c851f7@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®