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 3/4] Documentation/scheduler/sched-deadline.txt: improve and clarify AC bits
Date: Wed, 03 Sep 2014 10:37:01 +0200 [thread overview]
Message-ID: <5406D32D.9030306@unitn.it> (raw)
In-Reply-To: <CAM6o_m3VXiJO3ED_Rb-_Kfaw7mFyw_s4W0quQ_hSbpxgA_foLA@mail.gmail.com>
On 09/03/2014 09:48 AM, Henrik Austad wrote:
> On Wed, Sep 3, 2014 at 8:49 AM, Luca Abeni <luca.abeni@unitn.it> wrote:
>
>> Hi,
>>
>> On 09/02/2014 11:45 PM, Henrik Austad wrote:
>> [...]
>>
>> + On multiprocessor systems with global EDF scheduling (non partitioned
>>>> + systems), a sufficient test for schedulability can not be based on the
>>>> + utilisations (it can be shown that task sets with utilisations slightly
>>>> + larger than 1 can miss deadlines regardless of the number of CPUs M).
>>>> + However, as previously stated, enforcing that the total utilisation is
>>>> smaller
>>>> + than M is enough to guarantee that non real-time tasks are not starved
>>>> and
>>>> + that the tardiness of real-time tasks has an upper bound.
>>>>
>>>
>>> I'd _really_ appreciate a link to a paper where all of this is presented
>>> and proved!
>>>
>> Well, my original plan was to add the bibliography in the next round of
>> patches...
>> Is this ok?
>>
>
> Sure, but I don't see why you cannot add this now
Well, there are multiple papers to be cited here: the one showing that
in a pathological case you can have missed deadlines on M CPUs with utilisation
slightly larger than 1 (Dhall's effect), one or more papers presenting a more
advanced admission control for global EDF, one or more papers showing the tardiness
bound, ...
So, I'd like to spend some time doing some research to properly cite the most
appropriate references.
> you (or Juri?) did update one of the papers in this series, right?
In patch 1, I updated the URL for a publically available technical report I wrote
in 1998 (the old URL was in a web site I cannot access anymore, so I changed the
URL to point to a web site I can control).
> As long as an article with all the headache ends up here, I'm happy :)
As said, if possible I'd like to do it in the next batch of patches, so that
these updates are not delayed... If this is not ok, I'll update the patch
adding some references, but this will take some time.
Thanks,
Luca
next prev parent reply other threads:[~2014-09-03 8:37 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
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 [this message]
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=5406D32D.9030306@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