From: Luca Abeni <luca.abeni@unitn.it>
To: peterz@infradead.org
Cc: henrik@austad.us, juri.lelli@gmail.com, raistlin@linux.it,
mingo@kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, Luca Abeni <luca.abeni@unitn.it>
Subject: [PATCH 0/8] SCHED_DEADLINE documentation update
Date: Fri, 10 Apr 2015 12:19:47 +0200 [thread overview]
Message-ID: <1428661195-9609-1-git-send-email-luca.abeni@unitn.it> (raw)
Hi all,
here is an update for Documentation/scheduler/sched-deadline.txt.
Respect to the RFC I sent few days ago, I:
1) Split the patches in a better way, (so that, for example, Zhiqiang Zhang's
authorship is preserved)
2) Tried to address all the comments I received on the RFC
3) Added another patch, to split Section 3 in various subsections.
I think it is more readable in this way. Anyway, this is the last patch,
so it can easily be skipped if people do not like it.
I also split in a separate patch the discussion about the relationship between
tasks' parameters and SCHED_DEADLINE parameters. This is (I think) the only
part of the patchset that has not been previously discussed; I decided to
isolate it in its own patch so that other patches can be applied anyway.
Thanks,
Luca
Luca Abeni (7):
Documentation/scheduler/sched-deadline.txt: fix typos
Documentation/scheduler/sched-deadline.txt: use consistent namings
Documentation/scheduler/sched-deadline.txt: remove _i from sum, max
and min
Documentation/scheduler/sched-deadline.txt: Some notes on EDF
schedulability
Documentation/scheduler/sched-deadline.txt: add some references
Documentation/scheduler/sched-deadline.txt: relationship between
tasks' deadlines and scheduling deadlines
Documentation/scheduler/sched-deadline.txt: Split Section 3
Zhiqiang Zhang (1):
Documentation/scheduler/sched-deadline.txt: correct definition of
density as C_i/min{D_i,P_i}
Documentation/scheduler/sched-deadline.txt | 161 ++++++++++++++++++++++++----
1 file changed, 142 insertions(+), 19 deletions(-)
--
1.7.9.5
next reply other threads:[~2015-04-10 10:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 10:19 Luca Abeni [this message]
2015-04-10 10:19 ` [PATCH 1/8] Documentation/scheduler/sched-deadline.txt: correct definition of density as C_i/min{D_i,P_i} Luca Abeni
2015-04-10 10:19 ` [PATCH 2/8] Documentation/scheduler/sched-deadline.txt: fix typos Luca Abeni
2015-04-10 10:19 ` [PATCH 3/8] Documentation/scheduler/sched-deadline.txt: use consistent namings Luca Abeni
2015-04-10 10:19 ` [PATCH 4/8] Documentation/scheduler/sched-deadline.txt: remove _i from sum, max and min Luca Abeni
2015-04-10 10:19 ` [PATCH 5/8] Documentation/scheduler/sched-deadline.txt: Some notes on EDF schedulability Luca Abeni
2015-04-10 10:19 ` [PATCH 6/8] Documentation/scheduler/sched-deadline.txt: add some references Luca Abeni
2015-04-10 10:19 ` [PATCH 7/8] Documentation/scheduler/sched-deadline.txt: relationship between tasks' deadlines and scheduling deadlines Luca Abeni
2015-04-10 10:19 ` [PATCH 8/8] Documentation/scheduler/sched-deadline.txt: Split Section 3 Luca Abeni
2015-04-11 12:50 ` [PATCH 0/8] SCHED_DEADLINE documentation update Henrik Austad
2015-04-12 9:47 ` Ingo Molnar
2015-04-13 12:39 ` Luca Abeni
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=1428661195-9609-1-git-send-email-luca.abeni@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=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
all inboxes | Powered by JetHome®