From: Luca Abeni <luca.abeni@unitn.it>
To: Peter Zijlstra <peterz@infradead.org>, Henrik Austad <henrik@austad.us>
Cc: Luca Abeni <lucabe72@gmail.com>,
juri.lelli@gmail.com, raistlin@linux.it, mingo@kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [RFC 4/4] Documentation/scheduler/sched-deadline.txt: add some references
Date: Thu, 09 Apr 2015 12:08:36 +0200 [thread overview]
Message-ID: <55264FA4.5090805@unitn.it> (raw)
In-Reply-To: <20150409094427.GR5029@twins.programming.kicks-ass.net>
On 04/09/2015 11:44 AM, Peter Zijlstra wrote:
> On Thu, Apr 09, 2015 at 11:39:08AM +0200, Henrik Austad wrote:
>>> + CPUs, with the first M - 1 tasks having a small worst case execution time
>>> + WCET_i=e and period equal to relative deadline P_i=D_i=P-1. The last task
>>
>> Normally, 'e' is used to denote an _arbitrarily_ small value, and I suspect
>> that this is indeed the case here as well (you're going to describe
>> Dhall's effect, right?). Perhaps make that point explicit?
>>
>> T_i = {P_i, e, P_i}
>
> We're talking about \epsilon here, right?
Right. I used "e" to make the thing more readable in a simple text document.
> Is it customary to use a regular 'e' in CS literature for that?
I do not know... I just wanted to use one single character, and to avoid the "\"
(which only makes sense to people using latex :)
But if you want I can use "epsilon" or "\epsilon"... Let me know
Thanks,
Luca
next prev parent reply other threads:[~2015-04-09 10:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 11:59 [RFC 0/4] SCHED_DEADLINE documentation update Luca Abeni
2015-04-08 11:59 ` [RFC 1/4] Documentation/scheduler/sched-deadline.txt: fix typos Luca Abeni
2015-04-08 11:59 ` [RFC 2/4] Documentation/scheduler/sched-deadline.txt: use consistent namings Luca Abeni
2015-04-08 11:59 ` [RFC 3/4] Documentation/scheduler/sched-deadline.txt: Some notes on EDF schedulability Luca Abeni
2015-04-09 9:06 ` Henrik Austad
2015-04-09 9:34 ` Luca Abeni
2015-04-09 10:10 ` Henrik Austad
2015-04-09 10:35 ` Luca Abeni
2015-04-08 11:59 ` [RFC 4/4] Documentation/scheduler/sched-deadline.txt: add some references Luca Abeni
2015-04-08 14:43 ` Peter Zijlstra
2015-04-09 8:24 ` Juri Lelli
2015-04-09 9:13 ` Luca Abeni
2015-04-09 9:39 ` Henrik Austad
2015-04-09 9:44 ` Peter Zijlstra
2015-04-09 10:08 ` Luca Abeni [this message]
2015-04-09 10:11 ` Peter Zijlstra
2015-04-09 10:13 ` Henrik Austad
2015-04-09 11:55 ` Ingo Molnar
2015-04-09 10:05 ` Luca Abeni
2015-04-09 10:17 ` Henrik Austad
2015-04-08 14:44 ` [RFC 0/4] SCHED_DEADLINE documentation update Peter Zijlstra
2015-04-09 9:13 ` Luca Abeni
2015-04-09 9:17 ` Peter Zijlstra
2015-04-09 9:19 ` Luca Abeni
2015-04-09 9:29 ` Peter Zijlstra
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=55264FA4.5090805@unitn.it \
--to=luca.abeni@unitn.it \
--cc=henrik@austad.us \
--cc=juri.lelli@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucabe72@gmail.com \
--cc=mingo@kernel.org \
--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 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).