linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Valentin Schneider <valentin.schneider@arm.com>,
	John Mathew <john.mathew@unikie.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	corbet@lwn.net, mingo@redhat.com, peterz@infradead.org,
	juri.lelli@redhat.com, vincent.guittot@linaro.org,
	rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
	bristot@redhat.com, tsbogend@alpha.franken.de,
	lukas.bulwahn@gmail.com, x86@kernel.org,
	linux-mips@vger.kernel.org, tglx@linutronix.de,
	mostafa.chamanara@basemark.com, rdunlap@infradead.org,
	Oleg Tsymbal <oleg.tsymbal@unikie.com>
Subject: Re: [RFC PATCH v3 2/3] docs: scheduler: Add scheduler overview documentation
Date: Fri, 8 May 2020 12:58:36 +0200	[thread overview]
Message-ID: <b974b959-7b9a-2874-dca6-674b74ad5b42@arm.com> (raw)
In-Reply-To: <jhjh7wrtpjk.mognet@arm.com>

On 07/05/2020 23:15, Valentin Schneider wrote:
> 
> On 07/05/20 19:05, John Mathew wrote:

[...]

> It would also be an opportunity to have one place to (at least briefly)
> describe what the different sched classes do wrt capacity asymmetry - CFS
> does one thing, RT now does one thing (see Qais' work), and DL will
> hopefully soon follow (see Dietmar's work).
> 
> I'd be happy to contribute (some of) that, if it can be deemed useful (I
> personally think it might).

I like the idea.

Essentially all the code which is guarded by the 'if
(static_branch_unlikely(&sched_asym_cpucapacity)' condition or which
sets it during bring-up.

* 'Cpu capacity < SCHED_LOAD_SCALE for non-big' CPUs setting during
   bringup (necessary dt binding, CPUfreq influence)

* CFS capacity awareness:

  * wakeup - select_idle_capacity() (replaced wake_cap() & slow path to
             cover DynamIQ and classical big.LITTLE)

  * load_balance - misfit handling

* RT & DL capacity awareness

* ... & the relation to EAS (Documentation/scheduler/sched-energy.rst)

This is what we referred to (at least internally) as CAS (Capacity-Aware
Scheduling).

  reply	other threads:[~2020-05-08 10:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 18:05 [RFC PATCH v3 0/3] Add scheduler overview documentation John Mathew
2020-05-07 18:05 ` [RFC PATCH v3 1/3] docs: scheduler: Restructure scheduler documentation John Mathew
2020-05-07 18:05 ` [RFC PATCH v3 2/3] docs: scheduler: Add scheduler overview documentation John Mathew
2020-05-07 21:15   ` Valentin Schneider
2020-05-08 10:58     ` Dietmar Eggemann [this message]
2020-05-08 14:58       ` Valentin Schneider
2020-05-13 13:38       ` John Mathew
2020-05-13 13:33     ` John Mathew
2020-05-08 10:19   ` Dietmar Eggemann
2020-05-13 13:38     ` John Mathew
2020-05-08 15:36   ` Tao Zhou
2020-05-07 18:05 ` [RFC PATCH v3 3/3] docs: scheduler: Add introduction to scheduler context-switch John Mathew

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=b974b959-7b9a-2874-dca6-674b74ad5b42@arm.com \
    --to=dietmar.eggemann@arm.com \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=corbet@lwn.net \
    --cc=john.mathew@unikie.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=mostafa.chamanara@basemark.com \
    --cc=oleg.tsymbal@unikie.com \
    --cc=peterz@infradead.org \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=tsbogend@alpha.franken.de \
    --cc=valentin.schneider@arm.com \
    --cc=vincent.guittot@linaro.org \
    --cc=x86@kernel.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).