mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "tip-bot2 for Ricardo Neri" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	Christian Loehle <christian.loehle@arm.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Andrea Righi <arighi@nvidia.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: sched/core] sched/fair: Allow load balancing between CPUs of identical capacity
Date: Sat, 08 Aug 2026 09:44:47 -0000	[thread overview]
Message-ID: <178618228711.442315.10087514024728899315.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20260720-rneri-fix-cas-clusters-v6-5-bb500bf4afd4@linux.intel.com>

The following commit has been merged into the sched/core branch of tip:

Commit-ID:     7fd540b1bcaf59289e6e921463037d4eadc1d75b
Gitweb:        https://git.kernel.org/tip/7fd540b1bcaf59289e6e921463037d4eadc1d75b
Author:        Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
AuthorDate:    Mon, 20 Jul 2026 19:43:21 -07:00
Committer:     Peter Zijlstra <peterz@infradead.org>
CommitterDate: Fri, 07 Aug 2026 18:27:11 +02:00

sched/fair: Allow load balancing between CPUs of identical capacity

sched_balance_find_src_rq() avoids selecting a runqueue with a single
running task as busiest if doing so results in migrating the task to a
CPU with less than ~5% of extra capacity. It also unintentionally
prevents migrations between CPUs of identical capacity.

When CONFIG_SCHED_CLUSTER is enabled, load should be balanced across
clusters of CPUs with the same capacity. Allowing migration between CPUs
of identical capacity is necessary to meet this goal.

Use get_actual_cpu_capacity() to reflect architectural capacity as well
as diminished capacity due to hardware or cpufreq pressure. Guard this
check with the sched_cluster_active static key so that systems without
cluster topology are unaffected.

Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Christian Loehle <christian.loehle@arm.com>
Reviewed-by: Vincent Guittot <vincent.guittot@linaro.org>
Tested-by: Christian Loehle <christian.loehle@arm.com>
Tested-by: Andrea Righi <arighi@nvidia.com>
Link: https://patch.msgid.link/20260720-rneri-fix-cas-clusters-v6-5-bb500bf4afd4@linux.intel.com
---
 kernel/sched/fair.c |  9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index f1b4db3..dcf860c 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -13102,13 +13102,20 @@ static struct rq *sched_balance_find_src_rq(struct lb_env *env,
 		 */
 		if (env->sd->flags & SD_ASYM_CPUCAPACITY &&
 		    nr_running == 1) {
+			bool cluster_equal_cap = static_branch_unlikely(&sched_cluster_active) &&
+						 (get_actual_cpu_capacity(env->dst_cpu) ==
+						  get_actual_cpu_capacity(i));
 			bool smt_degraded_cap = sched_smt_active() && !is_core_idle(i);
 
 			/*
 			 * Busy SMT siblings reduce the capacity of CPU @i. Do
 			 * not skip it in this case.
+			 *
+			 * CONFIG_SCHED_CLUSTER requires balancing load across
+			 * clusters of identical capacity, accounting for
+			 * hardware and cpufreq pressure.
 			 */
-			if (!smt_degraded_cap &&
+			if (!smt_degraded_cap && !cluster_equal_cap &&
 			    !capacity_greater(capacity_of(env->dst_cpu), capacity))
 				continue;
 		}

  parent reply	other threads:[~2026-08-08  9:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21  2:43 [PATCH v6 0/6] sched: Fix cluster scheduling in the presence of asymmetric capacity Ricardo Neri
2026-07-21  2:43 ` [PATCH v6 1/6] sched/fair: Do not skip CPUs of similar capacity with busy SMT siblings Ricardo Neri
2026-08-08  9:44   ` [tip: sched/core] " tip-bot2 for Ricardo Neri
2026-07-21  2:43 ` [PATCH v6 2/6] sched/fair: Also gate overloaded status update for SD_ASYM_CPUCAPACITY Ricardo Neri
2026-08-08  9:44   ` [tip: sched/core] " tip-bot2 for Ricardo Neri
2026-07-21  2:43 ` [PATCH v6 3/6] sched/fair: Check CPU capacity before comparing group types during load balance Ricardo Neri
2026-08-08  9:44   ` [tip: sched/core] " tip-bot2 for Ricardo Neri
2026-07-21  2:43 ` [PATCH v6 4/6] sched/fair: Skip misfit load accounting when the destination CPU cannot help Ricardo Neri
2026-08-08  9:44   ` [tip: sched/core] " tip-bot2 for Ricardo Neri
2026-07-21  2:43 ` [PATCH v6 5/6] sched/fair: Allow load balancing between CPUs of identical capacity Ricardo Neri
2026-07-23  7:10   ` Christian Loehle
2026-08-04  9:55     ` Vincent Guittot
2026-08-06  3:34       ` Ricardo Neri
2026-08-04  9:50   ` Vincent Guittot
2026-08-08  9:44   ` tip-bot2 for Ricardo Neri [this message]
2026-07-21  2:43 ` [PATCH v6 6/6] sched/topology: Restore SD_PREFER_SIBLING in domains with asymmetric capacity Ricardo Neri
2026-08-04  9:56   ` Vincent Guittot
2026-08-08  9:44   ` [tip: sched/core] " tip-bot2 for 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=178618228711.442315.10087514024728899315.tip-bot2@tip-bot2 \
    --to=tip-bot2@linutronix.de \
    --cc=arighi@nvidia.com \
    --cc=christian.loehle@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=ricardo.neri-calderon@linux.intel.com \
    --cc=vincent.guittot@linaro.org \
    --cc=x86@kernel.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 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®