From: Andrea Righi <arighi@nvidia.com>
To: K Prateek Nayak <kprateek.nayak@amd.com>
Cc: Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
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: Wed, 22 Apr 2026 17:29:33 +0200 [thread overview]
Message-ID: <aejpXeGIdn-FXa9_@gpd4> (raw)
In-Reply-To: <d64f9802-4191-4b77-b315-9f0d88f83fb6@amd.com>
On Wed, Apr 22, 2026 at 09:06:40AM +0530, K Prateek Nayak wrote:
> Hello Andrea,
>
> On 4/21/2026 7:08 PM, Andrea Righi wrote:
> >> You can also try "best_fits <= -3" in that last bailout condition and
> >> see if that help.
> >
> > For the bailout condition I don't see much difference using either <= -3 or
> > == -4. In general, I see a small but consistent improvement with the SIS_UTIL
> > logic, especially when the system is close to saturation (as expected).
>
> Thank you for testing! I guess == -4 is safer then.
>
> It is probably best to add an enum of sorts to help distinguish these
> states rather than the magic numbers. Perhaps something like:
>
> enum asym_fits_state {
> /* In descending order of preference */
> ASYM_IDLE_CORE_UCLAMP_MISFIT = -4,
> ASYM_IDLE_CORE_COMPLETE_MISFIT,
> ASYM_IDLE_THREAD_FITS,
> ASYM_IDLE_THREAD_UCLAMP_MISFIT,
> ASYM_IDLE_COMPLETE_MISFIT,
>
> /* asym_fits_cpu() bias for an idle core. */
> ASYM_IDLE_CORE_BIAS = -3,
> };
>
> >
> > So, this looks good to me! Do you want me to include also this one in the new
> > SMT-aware asym cpu capacity patch series (keeping your authorship of course) or
> > do you prefer to route this separately?
>
> I think you can send it as a part of your series for easy review. I'll
> be happy to help reworking those bits based on the comments if folks
> aren't happy with them ;-)
BTW, the SIS_UTIL part also improves performance on Grace (tested also there to
make sure we were not regressing the non-SMT asym-cpu-capacity case).
So, definitely +1 to include this from me. :)
Thanks,
-Andrea
next prev parent reply other threads:[~2026-04-22 15:29 UTC|newest]
Thread overview: 21+ 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-22 3:36 ` K Prateek Nayak
2026-04-22 15:29 ` Andrea Righi [this message]
2026-04-21 12:26 ` Vincent Guittot
2026-04-21 12:33 ` Andrea Righi
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=aejpXeGIdn-FXa9_@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