archive mirror
 help / color / mirror / Atom feed
From: Dietmar Eggemann <>
To: Peter Zijlstra <>,
	Ley Foon Tan <>
Cc: Vincent Guittot <>,
	Ingo Molnar <>,
	Greg KH <>,, Quentin Perret <>
Subject: Re: sched: Question about big and little cores system with SMP and EAS
Date: Wed, 16 Jun 2021 15:20:30 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

- Quentin Perret <>
+ Quentin Perret <>

On 16/06/2021 13:39, Peter Zijlstra wrote:
> On Wed, Jun 16, 2021 at 07:29:26PM +0800, Ley Foon Tan wrote:
>> Hi all
>> Would like to ask the experts here regarding the Symmetric
>> Multi-Processing mode (SMP) with Energy aware scheduler (EAS) support
>> on the big + little cores system.
> And the you ask a question unrelated to either Symmetric MP or EAS :-)
>> Hardware system:
>> Big and little cores have almost the same ISA, but the big core has
>> some extension instructions that little core doesn't have.
> That problem is unrelated to big.Little / EAS, also by definition that
> is not SMP seeing how the 'S' is a blatant lie.
> The simplest solution is to simply disallow usage of the extended ISA
> and force mandate the common subset. The complicated answer is something
> along the lines of:

We don't encourage asymmetric ISA extensions for EAS*/CAS** on
big.Little systems.
It would be simply a nightmare to schedule tasks on such systems.

The exception to this is the 'asymmetric 32-bit Soc' to support 32bit
legacy Apps. The nightmare for scheduling is reduced in this case to CPU
affinity, something the task scheduler has to live with already today.
(+ DL admission control for 32bit tasks).

*  Documentation/scheduler/sched-energy.rst
** Documentation/scheduler/sched-capacity.rst

  reply	other threads:[~2021-06-16 13:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16 11:29 Ley Foon Tan
2021-06-16 11:39 ` Peter Zijlstra
2021-06-16 13:20   ` Dietmar Eggemann [this message]
2021-06-17  5:00     ` Ley Foon Tan
2021-06-17  7:51       ` Morten Rasmussen

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \
    --subject='Re: sched: Question about big and little cores system with SMP and EAS' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).