From: Tim Chen <tim.c.chen@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>,
Shrikanth Hegde <sshegde@linux.ibm.com>
Cc: Ingo Molnar <mingo@kernel.org>, Chen Yu <yu.c.chen@intel.com>,
Doug Nelson <doug.nelson@intel.com>,
Mohini Narkhede <mohini.narkhede@intel.com>,
linux-kernel@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Srikar Dronamraju <srikar@linux.ibm.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v4] sched/fair: Skip sched_balance_running cmpxchg when balance is not due
Date: Wed, 12 Nov 2025 13:10:15 -0800 [thread overview]
Message-ID: <c6fe7ac0f6de4d51705bb2f24f82df2c3018804f.camel@linux.intel.com> (raw)
In-Reply-To: <20251112112113.GO278048@noisy.programming.kicks-ass.net>
On Wed, 2025-11-12 at 12:21 +0100, Peter Zijlstra wrote:
> On Wed, Nov 12, 2025 at 04:39:43PM +0530, Shrikanth Hegde wrote:
> >
> >
>
> > > So perhaps this is the better option -- or did I overlook something with
> > > should_we_balance? It doesn't look like that will make a different
> > > decision on the retry.
> > >
> >
> > I think in newidle balance, these checks are there in swb to bail of load balance.
> > redo logic catches it right?
>
> Urgh, my brain still thinks we're not serializing on newidle. Perhaps I
> should make this 2 patches, one moving the serializing and one adding it
> to newidle.
>
> > env->dst_rq lock is taken only in attach_tasks, meanwhile, if the wakeup happened,
> > pending would be set. is irq enabled or remote CPU can set ttwu_pending on this rq?
> >
> > if (env->idle == CPU_NEWLY_IDLE) {
> > if (env->dst_rq->nr_running > 0 || env->dst_rq->ttwu_pending)
> > return 0;
> > return 1;
> > }
>
> Right, that could get tickled.
How about something like the following on top of v4 patch?
This will avoid releasing the lock and take care of the NEWLY_IDLE case.
Tim
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 43c5ec039633..26179f4b77f6 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -11772,14 +11772,13 @@ static int sched_balance_rq(int this_cpu, struct rq *this_rq,
.fbq_type = all,
.tasks = LIST_HEAD_INIT(env.tasks),
};
- bool need_unlock;
+ bool need_unlock = false;
cpumask_and(cpus, sched_domain_span(sd), cpu_active_mask);
schedstat_inc(sd->lb_count[idle]);
redo:
- need_unlock = false;
if (!should_we_balance(&env)) {
*continue_balancing = 0;
goto out_balanced;
@@ -11916,9 +11915,9 @@ static int sched_balance_rq(int this_cpu, struct rq *this_rq,
if (!cpumask_subset(cpus, env.dst_grpmask)) {
env.loop = 0;
env.loop_break = SCHED_NR_MIGRATE_BREAK;
- if (need_unlock)
- atomic_set_release(&sched_balance_running, 0);
-
+ if (env->idle == CPU_NEWLY_IDLE &&
+ (env->dst_running > 0 || env->dst_rq->ttwu_pending))
+ goto out;
goto redo;
}
goto out_all_pinned;
next prev parent reply other threads:[~2025-11-12 21:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 18:47 Tim Chen
2025-11-11 6:24 ` Shrikanth Hegde
2025-11-12 8:02 ` Srikar Dronamraju
2025-11-12 10:37 ` Peter Zijlstra
2025-11-12 10:45 ` Peter Zijlstra
2025-11-12 11:09 ` Shrikanth Hegde
2025-11-12 11:21 ` Peter Zijlstra
2025-11-12 21:10 ` Tim Chen [this message]
2025-11-13 4:25 ` Shrikanth Hegde
2025-11-13 17:49 ` Tim Chen
2025-11-12 11:25 ` Srikar Dronamraju
2025-11-12 13:39 ` Peter Zijlstra
2025-11-12 13:44 ` Peter Zijlstra
2025-11-12 16:02 ` Srikar Dronamraju
2025-11-12 10:53 ` Shrikanth Hegde
2025-11-14 12:19 ` [tip: sched/core] " tip-bot2 for Tim Chen
2025-11-15 20:56 ` Shrikanth Hegde
2025-11-17 18:55 ` Tim Chen
2025-11-17 19:00 ` K Prateek Nayak
2025-11-27 14:09 ` Peter Zijlstra
2025-11-18 9:54 ` Peter Zijlstra
2025-11-18 9:56 ` Peter Zijlstra
2025-11-21 6:26 ` Nathan Chancellor
2025-11-21 9:00 ` Peter Zijlstra
2025-11-17 19:06 ` Borislav Petkov
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=c6fe7ac0f6de4d51705bb2f24f82df2c3018804f.camel@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=doug.nelson@intel.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mohini.narkhede@intel.com \
--cc=peterz@infradead.org \
--cc=srikar@linux.ibm.com \
--cc=sshegde@linux.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=vincent.guittot@linaro.org \
--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®