From: Valentin Schneider <valentin.schneider@arm.com>
To: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Cc: mingo@kernel.org, peterz@infradead.org,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
morten.rasmussen@arm.com, Quentin Perret <qperret@google.com>,
Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH 0/3] sched: Document capacity aware scheduling
Date: Fri, 31 Jul 2020 20:20:13 +0100 [thread overview]
Message-ID: <20200731192016.7484-1-valentin.schneider@arm.com> (raw)
Hi,
This stems from John Mathew et al's documentation efforts; see the brief
exchange between Dietmar and I at [1].
This is written as a standalone documentation bit, the emphasis here being on
the "why" and "what" rather than the "how". I can try to rebase that on top of
John's series, but I think this could go in on its own.
[1]: https://lkml.kernel.org/r/b974b959-7b9a-2874-dca6-674b74ad5b42@arm.com
Cheers,
Valentin
Valentin Schneider (3):
sched: Document arch_scale_*_capacity()
sched/doc: Document capacity aware scheduling
sched/doc: Factorize bits between sched-energy.rst &
sched-capacity.rst
Documentation/scheduler/index.rst | 1 +
Documentation/scheduler/sched-capacity.rst | 439 +++++++++++++++++++++
Documentation/scheduler/sched-energy.rst | 12 +-
include/linux/sched/topology.h | 10 +
kernel/sched/sched.h | 10 +
5 files changed, 462 insertions(+), 10 deletions(-)
create mode 100644 Documentation/scheduler/sched-capacity.rst
--
2.27.0
next reply other threads:[~2020-07-31 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 19:20 Valentin Schneider [this message]
2020-07-31 19:20 ` [PATCH 1/3] sched: Document arch_scale_*_capacity() Valentin Schneider
2020-07-31 19:20 ` [PATCH 2/3] sched/doc: Document capacity aware scheduling Valentin Schneider
2020-08-04 11:26 ` peterz
2020-08-04 13:52 ` Valentin Schneider
2020-07-31 19:20 ` [PATCH 3/3] sched/doc: Factorize bits between sched-energy.rst & sched-capacity.rst Valentin Schneider
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=20200731192016.7484-1-valentin.schneider@arm.com \
--to=valentin.schneider@arm.com \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.org \
--cc=qperret@google.com \
--cc=vincent.guittot@linaro.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;
as well as URLs for NNTP newsgroup(s).