linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Juri Lelli <juri.lelli@arm.com>
To: Luca Abeni <luca.abeni@unitn.it>,
	Zhiqiang Zhang <zhangzhiqiang.zhang@huawei.com>
Cc: "henrik@austad.us" <henrik@austad.us>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"torvalds@linux-foundation.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: Wed, 08 Apr 2015 10:31:46 +0100	[thread overview]
Message-ID: <5524F582.5020201@arm.com> (raw)
In-Reply-To: <20150403125237.45b38a71@luca-1225C>

Hi Luca,

On 03/04/15 11:52, Luca Abeni wrote:
> Hi,
> 
> On Fri, 3 Apr 2015 16:18:33 +0800
> Zhiqiang Zhang <zhangzhiqiang.zhang@huawei.com> wrote:
> 
>> >From the contex,the definition of the destiny of a task
>> 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}.
> You are right, "T_i" should be substituted with "P_i"...
> But now that I look at it more carefully, I think that "C_i" is also
> wrong... It should be "WCET_i".
> 
> 
> BTW, speaking about documentation: I still have some SCHED_DEADLINE
> documentation patches in my local tree... I'll update and send them in
> next week. Juri, should I send the patches to you, or submit directly
> to the mailing list?
> 

As you prefer, I'll review them anyway :). I guess you can just
send them on the list if you like, so that you'll receive more
comments in one go.

Thanks a lot,

- Juri

> 			Thanks,
> 				Luca
>>
>> ----------------------------------------
>>
>> Signed-off-by: Zhiqiang Zhang <zhangzhiqiang.zhang@huawei.com>
>> ---
>>  Documentation/scheduler/sched-deadline.txt | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/Documentation/scheduler/sched-deadline.txt
>> b/Documentation/scheduler/sched-deadline.txt index 21461a0..194664b
>> 100644 --- a/Documentation/scheduler/sched-deadline.txt
>> +++ b/Documentation/scheduler/sched-deadline.txt
>> @@ -169,8 +169,8 @@ CONTENTS
>>   of all the tasks executing on a CPU if and only if the total
>> utilisation of the tasks running on such a CPU is smaller or equal
>> than 1. If D_i != P_i for some task, then it is possible to define
>> the density of
>> - 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 densities of the tasks running on such a CPU is smaller or
>> equal than 1 (notice that this condition is only sufficient, and not
>> necessary). 
> 


  reply	other threads:[~2015-04-08  9:31 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 [this message]
2015-04-08 10:34     ` Luca Abeni
2015-04-03 17:57 ` Henrik Austad
2015-04-03 19:47   ` Luca Abeni
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=5524F582.5020201@arm.com \
    --to=juri.lelli@arm.com \
    --cc=henrik@austad.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.abeni@unitn.it \
    --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).