linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xuewen Yan <xuewen.yan94@gmail.com>
To: Dietmar Eggemann <dietmar.eggemann@arm.com>
Cc: Christian Loehle <christian.loehle@arm.com>,
	Xuewen Yan <xuewen.yan@unisoc.com>,
	mingo@redhat.com,  peterz@infradead.org, juri.lelli@redhat.com,
	vincent.guittot@linaro.org,  rostedt@goodmis.org,
	bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
	 vdonnefort@google.com, ke.wang@unisoc.com,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] sched/feec: Simplify the traversal of pd'cpus
Date: Wed, 20 Aug 2025 19:09:23 +0800	[thread overview]
Message-ID: <CAB8ipk-bRR3hT-+42gAN6oRZzEkoKN5K1o+zpep14-RJthXETA@mail.gmail.com> (raw)
In-Reply-To: <7b3601d1-f39e-4691-84d1-8aa397e06535@arm.com>

On Tue, Aug 19, 2025 at 10:01 PM Dietmar Eggemann
<dietmar.eggemann@arm.com> wrote:
>
> On 19.08.25 03:02, Xuewen Yan wrote:
> > On Mon, Aug 18, 2025 at 11:24 PM Dietmar Eggemann
> > <dietmar.eggemann@arm.com> wrote:
> >>
> >> On 18.08.25 12:05, Xuewen Yan wrote:
> >>> On Fri, Aug 15, 2025 at 9:01 PM Dietmar Eggemann
> >>> <dietmar.eggemann@arm.com> wrote:
> >>>>
> >>>> On 14.08.25 10:52, Xuewen Yan wrote:
> >>>>> Hi Dietmar,
> >>>>>
> >>>>> On Thu, Aug 14, 2025 at 4:46 PM Dietmar Eggemann
> >>>>> <dietmar.eggemann@arm.com> wrote:
> >>>>>>
> >>>>>> On 12.08.25 10:33, Xuewen Yan wrote:
>
> [...]
>
> >> Looks like we do need also the sd cpumask here.
> >>
> >> Consider this tri-gear system:
> >>
> >> #  cat /sys/devices/system/cpu/cpu*/cpu_capacity
> >> 160
> >> 160
> >> 160
> >> 160
> >> 498
> >> 498
> >> 1024
> >> 1024
> >>
> >> and 2 exclusive cpusets cs1={0-1,4,6} and cs2={2-3,5,7}, so EAS is
> >> possible in all 3 root_domains (/, /cs1, /cs2):
> >
> > Isn't your CPU an ARM Dynamiq architecture?
> > In my understanding, for Dynamiq arch, there is only one MC domain...
> > Did I miss something?
>
> Ah, should have mentioned that this is qemu. I used a dts file
> (qemu-system-aarch64 ... -dtb foo.dtb) with individual
> 'next-level-cache' entries for the CPUs {0-3}, {4-5} and {6-7} so that's
> why you see MC & PKG. Removing those gives you a system with only MC:

Thank you for your patience in explaining:)
Looks like we do need also the sd cpumask here.

Thanks!

>
> [  106.986828] CPU2 attaching sched-domain(s):
> [  106.987846]  domain-0: span=2-3,5,7 level=MC
> [  106.987941]   groups: 2:{ span=2 cap=159 }, 3:{ span=3 cap=154 }, 5:{
> span=5 cap=495 }, 7:{ span=7 cap=991 }
> [  106.988842] CPU3 attaching sched-domain(s):
> [  106.989096]  domain-0: span=2-3,5,7 level=MC
> [  106.989136]   groups: 3:{ span=3 cap=154 }, 5:{ span=5 cap=495 }, 7:{
> span=7 cap=991 }, 2:{ span=2 cap=159 }
> [  106.989679] CPU5 attaching sched-domain(s):
> [  106.989692]  domain-0: span=2-3,5,7 level=MC
> [  106.989773]   groups: 5:{ span=5 cap=495 }, 7:{ span=7 cap=991 }, 2:{
> span=2 cap=159 }, 3:{ span=3 cap=154 }
> [  106.990466] CPU7 attaching sched-domain(s):
> [  106.990482]  domain-0: span=2-3,5,7 level=MC
> [  106.990632]   groups: 7:{ span=7 cap=991 }, 2:{ span=2 cap=159 }, 3:{
> span=3 cap=154 }, 5:{ span=5 cap=495 }
> [  106.997604] root domain span: 2-3,5,7
> [  106.998267] CPU0 attaching sched-domain(s):
> [  106.998278]  domain-0: span=0-1,4,6 level=MC
> [  106.998295]   groups: 0:{ span=0 cap=159 }, 1:{ span=1 cap=160 }, 4:{
> span=4 cap=496 }, 6:{ span=6 cap=995 }
> [  106.998584] CPU1 attaching sched-domain(s):
> [  106.998592]  domain-0: span=0-1,4,6 level=MC
> [  106.998604]   groups: 1:{ span=1 cap=160 }, 4:{ span=4 cap=496 }, 6:{
> span=6 cap=995 }, 0:{ span=0 cap=159 }
> [  106.999477] CPU4 attaching sched-domain(s):
> [  106.999487]  domain-0: span=0-1,4,6 level=MC
> [  106.999504]   groups: 4:{ span=4 cap=496 }, 6:{ span=6 cap=995 }, 0:{
> span=0 cap=159 }, 1:{ span=1 cap=160 }
> [  107.000070] CPU6 attaching sched-domain(s):
> [  107.000082]  domain-0: span=0-1,4,6 level=MC
> [  107.000095]   groups: 6:{ span=6 cap=995 }, 0:{ span=0 cap=159 }, 1:{
> span=1 cap=160 }, 4:{ span=4 cap=496 }
> [  107.000721] root domain span: 0-1,4,6
> [  107.001152] root_domain 2-3,5,7: pd6:{ cpus=6-7 nr_pstate=4 } pd4:{
> cpus=4-5 nr_pstate=4 } pd0:{ cpus=0-3 nr_pstate=4 }
> [  107.001869] root_domain 0-1,4,6: pd6:{ cpus=6-7 nr_pstate=4 } pd4:{
> cpus=4-5 nr_pstate=4 } pd0:{ cpus=0-3 nr_pstate=4 }
>
> [...]

      reply	other threads:[~2025-08-20 11:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-12  9:33 [RFC PATCH] sched/feec: Simplify the traversal of pd'cpus Xuewen Yan
2025-08-12 21:29 ` Christian Loehle
2025-08-14  8:46 ` Dietmar Eggemann
2025-08-14  9:52   ` Xuewen Yan
2025-08-15 13:01     ` Dietmar Eggemann
2025-08-18 11:05       ` Xuewen Yan
2025-08-18 15:24         ` Dietmar Eggemann
2025-08-19  2:02           ` Xuewen Yan
2025-08-19 14:01             ` Dietmar Eggemann
2025-08-20 11:09               ` Xuewen Yan [this message]

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=CAB8ipk-bRR3hT-+42gAN6oRZzEkoKN5K1o+zpep14-RJthXETA@mail.gmail.com \
    --to=xuewen.yan94@gmail.com \
    --cc=bsegall@google.com \
    --cc=christian.loehle@arm.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=ke.wang@unisoc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vdonnefort@google.com \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    --cc=xuewen.yan@unisoc.com \
    /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).