All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Juri Lelli <juri.lelli@arm.com>, peterz@infradead.org
Cc: luca.abeni@unitn.it, mingo@redhat.com, henrik@austad.us,
	raistlin@linux.it, juri.lelli@gmail.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] Documentation/scheduler/sched-deadline.txt: fix terminology and improve clarity
Date: Tue, 12 Aug 2014 10:45:16 -0700	[thread overview]
Message-ID: <53EA52AC.1040504@infradead.org> (raw)
In-Reply-To: <1407858555-14371-2-git-send-email-juri.lelli@arm.com>

On 08/12/14 08:49, Juri Lelli wrote:
> From: Luca Abeni <luca.abeni@unitn.it>
> 
> ---
>  Documentation/scheduler/sched-deadline.txt |   32 +++++++++++++++-------------
>  1 file changed, 17 insertions(+), 15 deletions(-)
> 
> diff --git a/Documentation/scheduler/sched-deadline.txt b/Documentation/scheduler/sched-deadline.txt
> index 18adc92..db25eb5 100644
> --- a/Documentation/scheduler/sched-deadline.txt
> +++ b/Documentation/scheduler/sched-deadline.txt
> @@ -147,6 +147,8 @@ CONTENTS
>   and the absolute deadlines (d_j) coincide, so a proper admission control
>   allows to respect the jobs' absolute deadlines for this task (this is what is
>   called "hard schedulability property" and is an extension of Lemma 1 of [2]).
> + Notice that if runtime > deadine the admission control will surely reject

                             deadline

> + this task, as it is not possible to respect its temporal constraints.
>  
>   References:
>    1 - C. L. Liu and J. W. Layland. Scheduling algorithms for multiprogram-


-- 
~Randy

  reply	other threads:[~2014-08-12 17:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12 15:49 [PATCH 0/4] SCHED_DEADLINE documentation fixes and improvements Juri Lelli
2014-08-12 15:49 ` [PATCH 1/4] Documentation/scheduler/sched-deadline.txt: fix terminology and improve clarity Juri Lelli
2014-08-12 17:45   ` Randy Dunlap [this message]
2014-08-13  9:03     ` Juri Lelli
2014-08-12 15:49 ` [PATCH 2/4] Documentation/scheduler/sched-deadline.txt: Rewrite section 4 intro Juri Lelli
2014-08-12 15:49 ` [PATCH 3/4] Documentation/scheduler/sched-deadline.txt: improve and clarify AC bits Juri Lelli
2014-08-12 18:11   ` Randy Dunlap
2014-08-12 20:17     ` Peter Zijlstra
2014-08-12 21:22     ` luca abeni
2014-08-13  9:05       ` Juri Lelli
2014-08-12 15:49 ` [PATCH 4/4] Documentation/scheduler/sched-deadline.txt: add tests suite appendix Juri Lelli
2014-08-12 17:57   ` Randy Dunlap
2014-08-13  9:09     ` Juri Lelli

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=53EA52AC.1040504@infradead.org \
    --to=rdunlap@infradead.org \
    --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=luca.abeni@unitn.it \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=raistlin@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.