From: Tim Chen <tim.c.chen@linux.intel.com>
To: Kayra Cizmeci <kayracizmeci@gmail.com>,
peterz@infradead.org, mingo@redhat.com, juri.lelli@redhat.com,
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>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Ricardo Neri <ricardo.neri-calderon@linux.intel.com>,
Chen Yu <yu.c.chen@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sched/cache: Ignore non-fair current in alb_break_llc()
Date: Tue, 20 Oct 2026 13:02:01 -0700 [thread overview]
Message-ID: <96c89ebc2cd7f8217e0053a7e5302594fb039683.camel@linux.intel.com> (raw)
In-Reply-To: <20261020185402.57017-1-kayracizmeci@gmail.com>
On Tue, 2026-10-20 at 21:54 +0300, Kayra Cizmeci wrote:
> Commit d6b9afab44e23 ("sched/cache: Fix
> checking active load balance by only considering the CFS task")
> stopped using task_util() for non-fair cur.
>
> __active_load_balance_cpu_stop() calls detach_one_task(), that only looks
> to cfs_tasks list. So if the rq->curr is not fair, doing a decision
> according to it is wrong, since we only migrate tasks that is fair.
>
> Commit f0d243a96f26 ("sched/fair: Avoid creating misfits during
> cache-aware balancing") passes cur to task_misfits_asym_cpu()
> without checking if the cur is in fair class or not. Fix this.
Sent out a suggested update to the commit log of v1 before I saw v2.
This updated log and patch looks okay to me.
Reviewed-by: Tim Chen <tim.c.chen@linux.intel.com>
Tim
>
> Fixes: f0d243a96f26 ("sched/fair: Avoid creating misfits during cache-aware balancing")
> Signed-off-by: Kayra Cizmeci <kayracizmeci@gmail.com>
> ---
> Changes v1->v2:
> * Add suggested comment (Tim Chen :>)
> * Change the changelog so that it says the issue is passing a
> non-fair cur to task_misfits_asym_cpu()
>
> This versions not compile-tested. Tho only change is this comment,
> so it should be fine. Right? ;-).
>
> 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 0feec172fd37..9d7fd6cec376 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -11016,7 +11016,14 @@ alb_break_llc(struct lb_env *env)
> return true;
>
> cur = rcu_dereference_all(env->src_rq->curr);
> - if (cur && cur->sched_class == &fair_sched_class)
> + /*
> + * Active balance only detaches CFS tasks, so a non-fair
> + * curr is never migrated. Ignore it and avoid using its
> + * stale util in the misfit and LLC checks.
> + */
> + if (cur && cur->sched_class != &fair_sched_class)
> + cur = NULL;
> + if (cur)
> util = task_util(cur);
>
> if (task_misfits_asym_cpu(env, cur) ||
prev parent reply other threads:[~2026-10-20 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 18:54 Kayra Cizmeci
2026-10-20 20:02 ` Tim Chen [this message]
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=96c89ebc2cd7f8217e0053a7e5302594fb039683.camel@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kayracizmeci@gmail.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=ricardo.neri-calderon@linux.intel.com \
--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®