mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tim Chen <tim.c.chen@linux.intel.com>
To: Jemmy Wong <jemmywong512@gmail.com>,
	mingo@redhat.com, peterz@infradead.org, 	kprateek.nayak@amd.com,
	yu.c.chen@intel.com
Cc: juri.lelli@redhat.com, vincent.guittot@linaro.org,
	dietmar.eggemann@arm.com, 	rostedt@goodmis.org,
	bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
		linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sched/cache: Avoid publishing partial LLC utilization
Date: Tue, 13 Oct 2026 10:11:49 -0700	[thread overview]
Message-ID: <98a75f35d1f382e35f19a6cca87935ca41339c66.camel@linux.intel.com> (raw)
In-Reply-To: <20261013084338.55100-1-jemmywong512@gmail.com>

On Tue, 2026-10-13 at 16:43 +0800, Jemmy Wong wrote:
> update_sg_lb_stats() sums utilization over the CPUs in both
> sched_group_span(group) and env->cpus, but takes capacity from
> group->sgc->capacity for the whole group. record_sg_llc_stats()
> publishes both.
> 
> Rejecting an all-affinity-pinned source runqueue removes that CPU from
> env->cpus and retries group selection. The retry can publish the
> partial utilization with the full capacity.
> 
> can_migrate_llc() then treats a busy preferred LLC as having spare
> capacity. More tasks can aggregate into it, migrations out can be
> blocked, and two busy LLCs may not fall back to generic balancing.
> This increases CPU contention and task latency. Found by inspection.
> 
> Skip publication on affinity retries using LBF_ALL_PINNED, retaining
> the first-pass snapshots and avoiding repeated cpumask checks. On the
> first pass, publish either shared LLC statistic only when env->cpus
> covers the whole group. Load balancing still uses the affinity-filtered
> statistics.
> 
> The same window exists during CPU hotplug. env->cpus drops a CPU at
> set_cpu_active(false), but the group span and sgc->capacity still
> include it until cpuset_cpu_inactive() rebuilds the domains. Keeping
> the previous snapshot avoids the mismatched publish. After the rebuild,
> the next periodic balance records both statistics again.
> 
> Suggested-by: K Prateek Nayak <kprateek.nayak@amd.com>
> Suggested-by: Tim Chen <tim.c.chen@linux.intel.com>
> Fixes: f025ef275388 ("sched/cache: Record per LLC utilization to guide cache aware scheduling decisions")
> Signed-off-by: Jemmy Wong <jemmywong512@gmail.com>

BTW, I think this is also a candidate for 7.2.x stable.

Tim

> ---
> 
> v1: https://lore.kernel.org/r/20261010113425.34829-1-jemmywong512@gmail.com/
> 
> Changes since v1:
> - Skip publication on affinity retries using LBF_ALL_PINNED, retaining
>   first-pass snapshots and avoiding repeated cpumask checks, as suggested
>   by Prateek and Tim. Keep cpumask_subset() for partial group coverage
>   during CPU hotplug on the first pass.
> - Update the comment and commit message to explain the retry behavior.
> - Add Fixes and Suggested-by tags.
> 
>  kernel/sched/fair.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 57360f5cdde4..dc01fdc0526d 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -12111,6 +12111,14 @@ static void record_sg_llc_stats(struct lb_env *env,
>  	if (env->sd->child != rcu_dereference_all(per_cpu(sd_llc, env->dst_cpu)))
>  		return;
> 
> +	/*
> +	 * A redo repeats stats published on the first pass. Hotplug can
> +	 * still leave env->cpus partial, so util would not match capacity.
> +	 */
> +	if ((env->flags & LBF_ALL_PINNED) ||
> +	    !cpumask_subset(sched_group_span(group), env->cpus))
> +		return;
> +
>  	/*
>  	 * At this point we know this group spans a LLC domain.
>  	 * Record the statistic of this group in its corresponding
> 
> --
> 2.54.0 (Apple Git-157)
> 

  parent reply	other threads:[~2026-10-13 17:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13  8:43 Jemmy Wong
2026-10-13 17:09 ` Tim Chen
2026-10-13 17:11 ` Tim Chen [this message]
2026-10-15 12:00   ` Jemmy Wong
2026-10-14 15:32 ` Chen Yu

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=98a75f35d1f382e35f19a6cca87935ca41339c66.camel@linux.intel.com \
    --to=tim.c.chen@linux.intel.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=jemmywong512@gmail.com \
    --cc=juri.lelli@redhat.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=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®