From: Daniel Bristot de Oliveira <bristot@redhat.com>
To: Alessio Balsini <alessio.balsini@arm.com>, linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Luca Abeni <luca.abeni@santannapisa.it>,
Tommaso Cucinotta <tommaso.cucinotta@santannapisa.it>
Subject: Re: [PATCH] sched/deadline: comment update for constrained deadline tasks explanation
Date: Fri, 24 Nov 2017 16:56:14 +0100 [thread overview]
Message-ID: <f6dc63d8-6afc-4a0b-2fcf-9aaf9a8d8fc6@redhat.com> (raw)
In-Reply-To: <1511521941-26952-1-git-send-email-alessio.balsini@arm.com>
On 11/24/2017 12:12 PM, Alessio Balsini wrote:
> Remove the adjective "relative" associated to the period of a periodic
> task, since the period is an absolute value.
>
> Rephrased the comment with the aim of making it even more clear.
>
> Signed-off-by: Alessio Balsini <alessio.balsini@arm.com>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Juri Lelli <juri.lelli@redhat.com>
> Cc: Daniel Bristot de Oliveira <bristot@redhat.com>
> Cc: Luca Abeni <luca.abeni@santannapisa.it>
> Cc: Tommaso Cucinotta <tommaso.cucinotta@santannapisa.it>
> Cc: linux-kernel@vger.kernel.org
> ---
> kernel/sched/deadline.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
> index f349f7e..902b2e0 100644
> --- a/kernel/sched/deadline.c
> +++ b/kernel/sched/deadline.c
> @@ -770,9 +770,9 @@ update_dl_revised_wakeup(struct sched_dl_entity *dl_se, struct rq *rq)
> }
>
> /*
> - * Regarding the deadline, a task with implicit deadline has a relative
> - * deadline == relative period. A task with constrained deadline has a
> - * relative deadline <= relative period.
> + * Regarding periodic real-time tasks, a constrained deadline task has the
Not only periodic, but also sporadic. Moreover, for sporadic it is not
_period_, but _minimum inter-arrival time_...
IMHO, it is not worth to add such level of details, not even on articles
people do, it just turn the explanation more confuse. See this, in the
page 5:
http://www-users.cs.york.ac.uk/~robdavis/papers/MPSurveyv5.0.pdf
There is no mention for the kind of period.
> + * relative deadline <= period. An implicit deadline task is a particular case
It is important to keep the "relative" to avoid confusion with the
variable "period" which is the "absolute period." I put relative to
helps with the ambiguity of the term "period."
-- Daniel
prev parent reply other threads:[~2017-11-24 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 11:12 Alessio Balsini
2017-11-24 15:56 ` Daniel Bristot de Oliveira [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=f6dc63d8-6afc-4a0b-2fcf-9aaf9a8d8fc6@redhat.com \
--to=bristot@redhat.com \
--cc=alessio.balsini@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@santannapisa.it \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tommaso.cucinotta@santannapisa.it \
/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®