From: Christian Loehle <christian.loehle@arm.com>
To: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>,
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>,
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
Subject: Re: [PATCH RESEND 2/4] sched/fair: Ignore misfit load if the destination CPU cannot help
Date: Wed, 1 Apr 2026 10:30:53 +0100 [thread overview]
Message-ID: <cca0188b-a39c-4e74-a4c6-3333775e6d98@arm.com> (raw)
In-Reply-To: <20260330-rneri-fix-cas-clusters-v1-2-1e465b6fecb2@linux.intel.com>
On 3/30/26 23:20, Ricardo Neri wrote:
> There is no point in identifying scheduling groups with misfit tasks if the
> destination CPU cannot help (i.e., it has less than 20% greater capacity
> than the most performant CPU in the group).
There's a mismatch here because capacity_greater() is 5%?
You could use 20% fits fits_capacity() I'd say it's too strict here.
>
> Since migrating misfit tasks takes precedence over relieving fully_busy
> groups, identifying a group with misfit tasks causes a destination CPU of
> smaller maximum capacity to back off (see capacity checks in update_sd_
> pick_busiest()) even if it can help: it could help a group of equally small
> maximum capacity if classified as fully_busy or has_spare.
>
> The described situation can happen if a scheduling domain has groups of
> big CPUs alongside two or more clusters of smaller CPUs that share L2
> cache. Load should be balanced between these sets of smaller CPUs when
> CONFIG_SCHED_CLUSTER is enabled.
>
> Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
> ---
> kernel/sched/fair.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 9da5014f8387..3c50ecffa4c7 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -10302,7 +10302,9 @@ static inline void update_sg_lb_stats(struct lb_env *env,
> if (local_group)
> continue;
>
> - if (sd_flags & SD_ASYM_CPUCAPACITY) {
> + /* Only look for misfit load if dst_cpu can help */
> + if (sd_flags & SD_ASYM_CPUCAPACITY &&
> + capacity_greater(capacity_of(env->dst_cpu), group->sgc->max_capacity)) {
> /* Check for a misfit task on the cpu */
> if (sgs->group_misfit_task_load < rq->misfit_task_load) {
> sgs->group_misfit_task_load = rq->misfit_task_load;
>
Apart from the above nit:
Reviewed-by: Christian Loehle <christian.loehle@arm.com>
next prev parent reply other threads:[~2026-04-01 9:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 22:20 [PATCH RESEND 0/4] sched: Fix cluster scheduling in the presence of asymmetric capacity Ricardo Neri
2026-03-30 22:20 ` [PATCH RESEND 1/4] sched/fair: Always skip fully_busy higher-capacity groups for load balance Ricardo Neri
2026-03-30 22:20 ` [PATCH RESEND 2/4] sched/fair: Ignore misfit load if the destination CPU cannot help Ricardo Neri
2026-04-01 9:30 ` Christian Loehle [this message]
2026-04-02 4:27 ` Ricardo Neri
2026-03-30 22:20 ` [PATCH RESEND 3/4] sched/fair: Allow load balancing between CPUs of equal capacity Ricardo Neri
2026-04-01 8:56 ` Christian Loehle
2026-04-02 4:30 ` Ricardo Neri
2026-03-30 22:20 ` [PATCH RESEND 4/4] sched/topology: Keep SD_PREFER_SIBLING for domains with clusters 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=cca0188b-a39c-4e74-a4c6-3333775e6d98@arm.com \
--to=christian.loehle@arm.com \
--cc=baohua@kernel.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.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-calderon@linux.intel.com \
--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 \
/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®