Re: [PATCH v2] sched/cache: Avoid publishing partial LLC utilization

[Chen Yu <chen.yu@linux.dev>]

On Tue, Oct 13, 2026 at 04:43:38PM +0800, Jemmy Wong wrote:
> Date: Tue, 13 Oct 2026 16:43:38 +0800
> From: Jemmy Wong <jemmywong512@gmail.com>
> To: mingo@redhat.com, peterz@infradead.org, tim.c.chen@linux.intel.com,
>  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, Jemmy
>  Wong <jemmywong512@gmail.com>
> Subject: [PATCH v2] sched/cache: Avoid publishing partial LLC utilization
> X-Mailer: git-send-email 2.54.0
> 
> Skip publication on affinity retries using LBF_ALL_PINNED, retaining
> the first-pass snapshots and avoiding repeated cpumask checks. On the

[ ... ]

> 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

It took me a while to understand the check of LBF_ALL_PINNED, to make it clear
how about adding comment below for future reference:

Once we enter record_sg_llc_stats(), LBF_ALL_PINNED being set is a
necessary and sufficient condition for being in a redo. Since
env->cpus may be incomplete when LBF_ALL_PINNED is set, and to avoid
recomputing the statistics of the same group during a redo, we skip
this update. The impact of skipping is small, because the interval
between the first pass and the subsequent redo is short.

Otherwise it looks good to me and

Reviewed-by: Chen Yu <yu.c.chen@intel.com>

thanks,
Chenyu