All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ley Foon Tan <lftan.linux@gmail.com>
To: Dietmar Eggemann <dietmar.eggemann@arm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Ingo Molnar <mingo@redhat.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, Quentin Perret <qperret@google.com>
Subject: Re: sched: Question about big and little cores system with SMP and EAS
Date: Thu, 17 Jun 2021 13:00:12 +0800	[thread overview]
Message-ID: <CAFiDJ5-j8UER1mGggC62C309T+t+y6-vy_NuKOJL6TQHrHAGtA@mail.gmail.com> (raw)
In-Reply-To: <c81ac071-c648-54ac-72ad-2dab0fa1dd4b@arm.com>

On Wed, Jun 16, 2021 at 9:20 PM Dietmar Eggemann
<dietmar.eggemann@arm.com> wrote:
>
> - Quentin Perret <quentin.perret@arm.com>
> + Quentin Perret <qperret@google.com>
>
> 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:
> >
> >   https://lkml.kernel.org/r/20210608180313.11502-1-will@kernel.org
>
> 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

Thanks for the reply.
Yes, forsee it is very complicated and nightmare for software to
support for SMP mode but HW is not real "symmetric".
That's why post the question here to ask the advice and comment from
experts here. So that can feedback to HW team.
Asymmetric extension instructions issue should more complicated than
asymmetric 32-bit app support, it can happen in all the areas (kernel,
app, library and etc).

Thanks!

Regards
Ley Foon

  reply	other threads:[~2021-06-17  5:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16 11:29 sched: Question about big and little cores system with SMP and EAS Ley Foon Tan
2021-06-16 11:39 ` Peter Zijlstra
2021-06-16 13:20   ` Dietmar Eggemann
2021-06-17  5:00     ` Ley Foon Tan [this message]
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:
  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=CAFiDJ5-j8UER1mGggC62C309T+t+y6-vy_NuKOJL6TQHrHAGtA@mail.gmail.com \
    --to=lftan.linux@gmail.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.