mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
To: Christian Loehle <christian.loehle@arm.com>
Cc: Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Valentin Schneider <vschneid@redhat.com>,
	Tim C Chen <tim.c.chen@linux.intel.com>,
	Chen Yu <yu.c.chen@intel.com>, Barry Song <baohua@kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Andrea Righi <arighi@nvidia.com>,
	K Prateek Nayak <kprateek.nayak@amd.com>,
	Len Brown <lenb@kernel.org>,
	ricardo.neri@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/6] sched/fair: Do not skip CPUs of similar capacity with busy SMT siblings
Date: Tue, 9 Jun 2026 20:32:50 -0700	[thread overview]
Message-ID: <20260610033250.GC30647@ranerica-svr.sc.intel.com> (raw)
In-Reply-To: <a086c53c-3691-4293-bc22-b2a94bd46f81@arm.com>

On Mon, Jun 08, 2026 at 02:50:38PM +0100, Christian Loehle wrote:
> On 6/8/26 13:57, Ricardo Neri wrote:
> > When picking a busiest CPU with only one running task, the function
> > sched_balance_find_src_rq() skips candidate CPUs if the destination CPU has
> > less than ~5% extra capacity. This condition only holds if all the SMT
> > siblings of a CPU are idle.
> > 
> > SMT siblings share the computing resources of a physical core and this
> > results in reduced capacity if more than one sibling is busy.
> > 
> > Skipping a CPU as described would prevent the load balancer from pulling
> > tasks from a scheduling group previously and correctly identified as
> > group_smt_balance (i.e., one with more than one task running).
> > 
> > Do not skip a candidate CPU of similar capacity if it has busy SMT
> > siblings.
> > 
> > Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
> 
> Nice find!
> Reviewed-by: Christian Loehle <christian.loehle@arm.com>

Thanks! I will make more changes based on feedback from Chen Yu and
Prateek. You may want to reissue your tag after that :)

  reply	other threads:[~2026-06-10  3:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-08 12:57 [PATCH v4 0/6] sched: Fix cluster scheduling in the presence of asymmetric capacity Ricardo Neri
2026-06-08 12:57 ` [PATCH v4 1/6] sched/fair: Do not skip CPUs of similar capacity with busy SMT siblings Ricardo Neri
2026-06-08 13:50   ` Christian Loehle
2026-06-10  3:32     ` Ricardo Neri [this message]
2026-06-09  4:26   ` K Prateek Nayak
2026-06-09  6:24     ` Chen, Yu C
2026-06-09  6:29       ` K Prateek Nayak
2026-06-10  3:29         ` Ricardo Neri
2026-06-08 12:57 ` [PATCH v4 2/6] sched/fair: Also gate overloaded status update for SD_ASYM_CPUCAPACITY Ricardo Neri
2026-06-08 12:57 ` [PATCH v4 3/6] sched/fair: Check CPU capacity before comparing group types during load balance Ricardo Neri
2026-06-08 12:57 ` [PATCH v4 4/6] sched/fair: Skip misfit load accounting when the destination CPU cannot help Ricardo Neri
2026-06-08 12:57 ` [PATCH v4 5/6] sched/fair: Allow load balancing between CPUs of identical capacity Ricardo Neri
2026-06-08 12:57 ` [PATCH v4 6/6] sched/topology: Do not clear SD_PREFER_SIBLING in domains with clusters Ricardo Neri
2026-06-08 17:37 ` [PATCH v4 0/6] sched: Fix cluster scheduling in the presence of asymmetric capacity Christian Loehle
2026-06-09  3:19   ` Ricardo Neri
2026-06-09 20:09     ` Christian Loehle
2026-06-10  3:28       ` Ricardo Neri

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=20260610033250.GC30647@ranerica-svr.sc.intel.com \
    --to=ricardo.neri-calderon@linux.intel.com \
    --cc=arighi@nvidia.com \
    --cc=baohua@kernel.org \
    --cc=bsegall@google.com \
    --cc=christian.loehle@arm.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.org \
    --cc=ricardo.neri@intel.com \
    --cc=rostedt@goodmis.org \
    --cc=tim.c.chen@linux.intel.com \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    --cc=yu.c.chen@intel.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

all inboxes | Powered by JetHome®