From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Quentin Perret <quentin.perret@arm.com>
Cc: Juri Lelli <juri.lelli@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Peter Zijlstra <peterz@infradead.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Ingo Molnar <mingo@redhat.com>,
Morten Rasmussen <morten.rasmussen@arm.com>,
qais.yousef@arm.com, Patrick Bellasi <patrick.bellasi@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] sched: Document Energy Aware Scheduling
Date: Fri, 18 Jan 2019 10:57:08 +0100 [thread overview]
Message-ID: <CAJZ5v0jw0BgmkwrtjuiC7YKO6A+k2eFfFDGtGsSWymW8PSTscA@mail.gmail.com> (raw)
In-Reply-To: <20190118091652.xn6iw52tccwh6vap@queper01-lin>
On Fri, Jan 18, 2019 at 10:16 AM Quentin Perret <quentin.perret@arm.com> wrote:
>
> Hi Juri,
>
> On Thursday 17 Jan 2019 at 16:51:17 (+0100), Juri Lelli wrote:
> > On 10/01/19 11:05, Quentin Perret wrote:
> [...]
> > > +The idea behind introducing an EM is to allow the scheduler to evaluate the
> > > +implications of its decisions rather than blindly applying energy-saving
> > > +techniques that may have positive effects only on some platforms. At the same
> > > +time, the EM must be as simple as possible to minimize the scheduler latency
> > > +impact.
> > > +
> > > +In short, EAS changes the way CFS tasks are assigned to CPUs. When it is time
> >
> > Not sure if we want to remark the fact that EAS is looking at CFS tasks
> > only ATM.
>
> Oh, what's wrong about mentioning it ? I mean, it is a fact ATM ...
But it won't hurt to mention that it may cover other scheduling
classes in the future. IOW, the scope limit is not fundamental.
> > > +for the scheduler to decide where a task should run (during wake-up), the EM
> > > +is used to break the tie between several good CPU candidates and pick the one
> > > +that is predicted to yield the best energy consumption without harming the
> > > +system's throughput. The predictions made by EAS rely on specific elements of
> > > +knowledge about the platform's topology, which include the 'capacity' of CPUs,
> >
> > Add a reference to DT bindings docs defining 'capacity' (or define it
> > somewhere)?
>
> Right, I can mention this is defined in the next section. But are you
> sure about the reference to the DT bindings ? They're arm-specific right ?
> Maybe I can give that as an example or something ...
Example sounds right.
You also can point to the section below from here.
Side note: If the doc is in the .rst format (which Peter won't like
I'm sure :-)), you can actually use cross-references in it and you get
a translation to an HTML doc (hosted at kernel.org) for free and the
cross-references become clickable links in that.
next prev parent reply other threads:[~2019-01-18 9:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 11:05 [PATCH 0/2] Documentation: Explain EAS and EM Quentin Perret
2019-01-10 11:05 ` [PATCH 1/2] PM / EM: Document the Energy Model framework Quentin Perret
2019-01-17 14:47 ` Juri Lelli
2019-01-17 14:53 ` Quentin Perret
2019-01-10 11:05 ` [PATCH 2/2] sched: Document Energy Aware Scheduling Quentin Perret
2019-01-17 15:51 ` Juri Lelli
2019-01-18 9:16 ` Quentin Perret
2019-01-18 9:57 ` Rafael J. Wysocki [this message]
2019-01-18 10:34 ` Quentin Perret
2019-01-18 10:58 ` Rafael J. Wysocki
2019-01-18 11:01 ` Rafael J. Wysocki
2019-01-18 11:11 ` Quentin Perret
2019-01-18 11:20 ` Rafael J. Wysocki
2019-01-18 11:26 ` Quentin Perret
2019-01-18 12:34 ` 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=CAJZ5v0jw0BgmkwrtjuiC7YKO6A+k2eFfFDGtGsSWymW8PSTscA@mail.gmail.com \
--to=rafael@kernel.org \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=patrick.bellasi@arm.com \
--cc=peterz@infradead.org \
--cc=qais.yousef@arm.com \
--cc=quentin.perret@arm.com \
--cc=rjw@rjwysocki.net \
/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).