From: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
To: 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>,
Christian Loehle <christian.loehle@arm.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Andrea Righi <arighi@nvidia.com>, Barry Song <baohua@kernel.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
ricardo.neri@intel.com, linux-kernel@vger.kernel.org,
Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Subject: [PATCH v6 5/6] sched/fair: Allow load balancing between CPUs of identical capacity
Date: Mon, 20 Jul 2026 19:43:21 -0700 [thread overview]
Message-ID: <20260720-rneri-fix-cas-clusters-v6-5-bb500bf4afd4@linux.intel.com> (raw)
In-Reply-To: <20260720-rneri-fix-cas-clusters-v6-0-bb500bf4afd4@linux.intel.com>
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.
Tested-by: Christian Loehle <christian.loehle@arm.com>
Tested-by: Andrea Righi <arighi@nvidia.com>
Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
---
Changes in v6:
* Switched to use get_actual_cpu_capacity() instead of
arch_scale_cpu_capacity(). The former considers rq->avg_hw.load_avg and
cpufreq_pressure and their impact on CPU capacity. (Vincent)
* Renamed the variable same_arch_cluster as cluster_equal_cap for
clarity. (Andrea)
* Added Tested-by tag from Andrea. Thanks!
Changes in v5:
* Optimized logic to identify same-arch clusters only when needed.
* Added Tested-by tag from Christian. Thanks!
Changes in v4:
* Implemented the check for cluster with a local variable for improved
readability.
Changes in v3:
* Reverted the inverted capacity check; the inverted form incorrectly
allows migrations to CPUs of slightly less capacity.
* Guarded the check for architectural capacity with the
sched_cluster_active static key.
Changes in v2:
* Used arch_scale_cpu_capacity() instead of capacity_of() to ignore
runtime variability.
* Inverted the check for runtime capacity. (Christian)
* Reworded patch description for clarity.
---
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 feea47e6abea..de4189b562ac 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -13104,13 +13104,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;
}
--
2.43.0
next prev parent reply other threads:[~2026-07-21 2:33 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 ` Ricardo Neri [this message]
2026-07-23 7:10 ` [PATCH v6 5/6] sched/fair: Allow load balancing between CPUs of identical capacity 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: sched/core] " tip-bot2 for Ricardo Neri
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=20260720-rneri-fix-cas-clusters-v6-5-bb500bf4afd4@linux.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®