From: Andrea Righi <arighi@nvidia.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: K Prateek Nayak <kprateek.nayak@amd.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
Christian Loehle <christian.loehle@arm.com>,
Koba Ko <kobak@nvidia.com>,
Felix Abecassis <fabecassis@nvidia.com>,
Balbir Singh <balbirs@nvidia.com>,
Shrikanth Hegde <sshegde@linux.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] sched/fair: Prefer fully-idle SMT cores in asym-capacity idle selection
Date: Tue, 21 Apr 2026 14:33:13 +0200 [thread overview]
Message-ID: <aeduiZ1Q1T8_c0sa@gpd4> (raw)
In-Reply-To: <CAKfTPtDGR6j9U8FFnCFV+ynhTvYQYNiCRbqKKpmf1fkcFkcewQ@mail.gmail.com>
On Tue, Apr 21, 2026 at 02:26:58PM +0200, Vincent Guittot wrote:
...
> > > > Yeah, makes sense. I'm wondering if we should attach the shared blob to
> > > > sd_asym_cpucapacity only when asym is a non-overlapping domain, otherwise
> > > > fallback to sd_llc and, in this case, ignore has_idle_cores in
> > > > select_idle_capacity(). This might be not the best in terms of efficiency on
> > > > those exotic topologies, but it'd eliminate the overlap/aliasing risk, while
> > > > still being correct. What do you think?
> > >
> > > I slightly changed your patch adding this logic on top, I'll send an updated
> > > patch series, so it's easier to review/comment.
> >
> > Actually... while preparing the series I realized that in select_idle_capacity()
> > we may end up clearing the has_idle_cores hint even when the failure is due to
> > affinity constraints (no fit CPU in the allowed cpumask), not only when no fully
> > idle core is found in the system and this can lead to false has_idle_cores
> > hints.
>
> How is it different from select_idle_cpu() which does the same afaict ?
Nah, it was just me not reading the code right. It's the same with
select_idle_cpu(), so I'm back at using Prateek's patch.
Thanks,
-Andrea
next prev parent reply other threads:[~2026-04-21 12:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 5:31 [PATCH v2 0/2] sched/fair: SMT-aware asymmetric CPU capacity Andrea Righi
2026-04-03 5:31 ` [PATCH 1/2] sched/fair: Prefer fully-idle SMT cores in asym-capacity idle selection Andrea Righi
2026-04-07 11:21 ` Dietmar Eggemann
2026-04-18 8:24 ` Andrea Righi
2026-04-20 5:49 ` K Prateek Nayak
2026-04-20 8:36 ` Andrea Righi
2026-04-20 9:39 ` K Prateek Nayak
2026-04-20 21:42 ` Andrea Righi
2026-04-21 9:01 ` Andrea Righi
2026-04-21 9:35 ` Andrea Righi
2026-04-21 11:22 ` K Prateek Nayak
2026-04-21 12:31 ` Andrea Righi
2026-04-21 13:38 ` Andrea Righi
2026-04-21 12:26 ` Vincent Guittot
2026-04-21 12:33 ` Andrea Righi [this message]
2026-04-17 9:39 ` Vincent Guittot
2026-04-18 6:02 ` Andrea Righi
2026-04-19 10:20 ` Vincent Guittot
2026-04-03 5:31 ` [PATCH 2/2] sched/fair: Reject misfit pulls onto busy SMT siblings on asym-capacity Andrea Righi
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=aeduiZ1Q1T8_c0sa@gpd4 \
--to=arighi@nvidia.com \
--cc=balbirs@nvidia.com \
--cc=bsegall@google.com \
--cc=christian.loehle@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=fabecassis@nvidia.com \
--cc=juri.lelli@redhat.com \
--cc=kobak@nvidia.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sshegde@linux.ibm.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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