linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Abeni <luca.abeni@unitn.it>
To: Henrik Austad <henrik@austad.us>
Cc: Zhiqiang Zhang <zhangzhiqiang.zhang@huawei.com>,
	juri.lelli@arm.com, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org
Subject: Re: [PATCH] Documentation/scheduler/sched-deadline.txt: correct definition of density as C_i/min{D_i,P_i}
Date: Fri, 3 Apr 2015 21:47:13 +0200	[thread overview]
Message-ID: <20150403214713.70e9614b@luca-1225C> (raw)
In-Reply-To: <20150403175737.GA3847@icarus.home.austad.us>

Hi Henrik,

On Fri, 3 Apr 2015 19:57:37 +0200
Henrik Austad <henrik@austad.us> wrote:
[...]
> > C_i/min{D_i,T_i},where T_i is not referred before, should be
> > substituted by C_i/min{D_i,P_i}.
> 
> Actually, I'd prefer we use T_i to describe the period and not P
> because:
> 
> - P is easy to confuse with priority - which has _nothing_ to do with 
>   deadline scheduling
> 
> - I was going to state that "the litterature is consistent in its
> usage of 'T_i' for task i's period". But then I dived through some of
> the books and of course it isn't. Buttazzo use T, Jane Liu use P and
> so on. However, I state that *most* litterature use T_i do denote the
> period of task i. Burns & Davis has a nice summary of RT-litterature
> [1].
I think literature is more or less equally divided between "P" and
"T" (I suspect I personally used different letters in different
papers :)


> So I'd rather prefer a s/P_i/T_i/ throughout the text.
> 
> I realise that I've reviewed quite a lot of this, and I have some
> vague memories of this being discussed earlier, Juri? Luca?
I remember there was a discussion (and I seem to remember that the
symbol used for the period was changed at least one time, but I might
be wrong), but I do not remember the details.

Next week I'll have some time for working on this; I'll search the old
emails and I'll try to reconstruct the discussion.

[...]
> > - a task as C_i/min{D_i,T_i}, and EDF is able to respect all the
> > deadlines
> > - of all the tasks running on a CPU if the sum sum_i
> > C_i/min{D_i,T_i} of the
> > + a task as C_i/min{D_i,P_i}, and EDF is able to respect all the
> > deadlines
> > + of all the tasks running on a CPU if the sum sum_i
> > C_i/min{D_i,P_i} of the
> 
> My argument for T_i vs. P_i aside, I do agree that we should not use
> T_i here whilst using P_i in other places. We should strive to be
> internally consistent above all else.
I fully agree with this ;-)


			Luca

  reply	other threads:[~2015-04-03 19:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03  8:18 [PATCH] Documentation/scheduler/sched-deadline.txt: correct definition of density as C_i/min{D_i,P_i} Zhiqiang Zhang
2015-04-03 10:52 ` Luca Abeni
2015-04-08  9:31   ` Juri Lelli
2015-04-08 10:34     ` Luca Abeni
2015-04-03 17:57 ` Henrik Austad
2015-04-03 19:47   ` Luca Abeni [this message]
2015-04-07  9:48     ` Luca Abeni

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=20150403214713.70e9614b@luca-1225C \
    --to=luca.abeni@unitn.it \
    --cc=henrik@austad.us \
    --cc=juri.lelli@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=zhangzhiqiang.zhang@huawei.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;
as well as URLs for NNTP newsgroup(s).