From: Luca Abeni <luca.abeni@unitn.it>
To: Henrik Austad <henrik@austad.us>
Cc: Juri Lelli <juri.lelli@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
rdunlap <rdunlap@infradead.org>, Ingo Molnar <mingo@redhat.com>,
Dario Faggioli <raistlin@linux.it>,
Juri Lelli <juri.lelli@gmail.com>,
LKML doc <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/4] Documentation/scheduler/sched-deadline.txt: fix terminology and improve clarity
Date: Wed, 03 Sep 2014 10:27:01 +0200 [thread overview]
Message-ID: <5406D0D5.8030001@unitn.it> (raw)
In-Reply-To: <CAM6o_m19T7OV=4_5rh_m1XSZKQmpKD0TaSSkiOxthNLz7uJ8Gw@mail.gmail.com>
On 09/03/2014 09:45 AM, Henrik Austad wrote:
[...]
>> Summing up, the CBS[2,3] algorithms assigns scheduling deadlines to
>>>> tasks so
>>>> that each task runs for at most its runtime every period, avoiding any
>>>> interference between different tasks (bandwidth isolation), while the
>>>> EDF[1]
>>>> - algorithm selects the task with the smallest scheduling deadline as
>>>> the one
>>>> + algorithm selects the task with the closest scheduling deadline as the
>>>> one
>>>> to be executed first. Thanks to this feature, also tasks that do not
>>>>
>>>
>>> s/first/next/
>>>
>>> Also, next sentence does not make much sense, I would drop the also;
>>>
>>> "Thanks to this feature, tasks that do not strictly comply with the ..."
>>>
>> I agree with these changes, but they are in text that is not changed by my
>> patch, right?
>> What should I do? Add these changes to the patch, or send an additional
>> incremental
>> patch with these changes?
>>
>
> Patch is about clarity, right? I'd just add it to this patch.
Ok; I'll send an updated patch to Juri.
Thanks,
Luca
next prev parent reply other threads:[~2014-09-03 8:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 10:00 [PATCH v3 0/4] SCHED_DEADLINE documentation fixes and improvements Juri Lelli
2014-08-28 10:00 ` [PATCH v3 1/4] Documentation/scheduler/sched-deadline.txt: fix terminology and improve clarity Juri Lelli
2014-09-02 21:10 ` Henrik Austad
2014-09-03 6:43 ` Luca Abeni
[not found] ` <CAM6o_m19T7OV=4_5rh_m1XSZKQmpKD0TaSSkiOxthNLz7uJ8Gw@mail.gmail.com>
2014-09-03 8:27 ` Luca Abeni [this message]
2014-09-04 8:46 ` Juri Lelli
2014-08-28 10:00 ` [PATCH v3 2/4] Documentation/scheduler/sched-deadline.txt: Rewrite section 4 intro Juri Lelli
2014-09-02 21:14 ` Henrik Austad
2014-09-04 8:57 ` Juri Lelli
2014-08-28 10:00 ` [PATCH v3 3/4] Documentation/scheduler/sched-deadline.txt: improve and clarify AC bits Juri Lelli
2014-09-02 21:45 ` Henrik Austad
2014-09-03 6:49 ` Luca Abeni
[not found] ` <CAM6o_m3VXiJO3ED_Rb-_Kfaw7mFyw_s4W0quQ_hSbpxgA_foLA@mail.gmail.com>
2014-09-03 8:37 ` Luca Abeni
2014-09-03 9:18 ` Juri Lelli
2014-09-04 9:25 ` Juri Lelli
2014-08-28 10:00 ` [PATCH v3 4/4] Documentation/scheduler/sched-deadline.txt: add tests suite appendix Juri Lelli
2014-09-02 21:53 ` Henrik Austad
2014-09-04 10:15 ` Juri Lelli
2014-09-02 21:55 ` [PATCH v3 0/4] SCHED_DEADLINE documentation fixes and improvements Henrik Austad
2014-09-03 8:46 ` Ingo Molnar
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=5406D0D5.8030001@unitn.it \
--to=luca.abeni@unitn.it \
--cc=henrik@austad.us \
--cc=juri.lelli@arm.com \
--cc=juri.lelli@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=raistlin@linux.it \
--cc=rdunlap@infradead.org \
/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