From: Peter Zijlstra <peterz@infradead.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Juri Lelli <juri.lelli@arm.com>,
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 3/4] Documentation/scheduler/sched-deadline.txt: improve and clarify AC bits
Date: Tue, 12 Aug 2014 22:17:04 +0200 [thread overview]
Message-ID: <20140812201704.GR19379@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <53EA58B4.8050307@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
On Tue, Aug 12, 2014 at 11:11:00AM -0700, Randy Dunlap wrote:
> > + wcet and its period (or minimum inter-arrival time), and represents
>
> "wcet" seems to be used here without any explanation of what it means.
Occupational deficiency I suppose: Worst Case Execution Time. Yes it
would be good to spell that out at least once.
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-08-12 20:17 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
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 [this message]
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=20140812201704.GR19379@twins.programming.kicks-ass.net \
--to=peterz@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=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
Powered by JetHome