From: Tim Chen <tim.c.chen@linux.intel.com>
To: Shrikanth Hegde <sshegde@linux.ibm.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Peter Zijlstra <peterz@infradead.org>
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>
Subject: Re: [PATCH v3] sched/fair: Skip sched_balance_running cmpxchg when balance is not due
Date: Fri, 07 Nov 2025 09:43:42 -0800 [thread overview]
Message-ID: <4fc95e1409d3218171a54e3baaa2e2a37d724add.camel@linux.intel.com> (raw)
In-Reply-To: <2edf1a85-4736-4e8b-bfc9-003dd1f34be7@linux.ibm.com>
On Fri, 2025-11-07 at 14:27 +0530, Shrikanth Hegde wrote:
>
> On 11/7/25 8:27 AM, K Prateek Nayak wrote:
> > Hello Tim,
> >
> > On 11/7/2025 4:57 AM, Tim Chen wrote:
> > > @@ -11757,6 +11772,7 @@ static int sched_balance_rq(int this_cpu, struct rq *this_rq,
> > > .fbq_type = all,
> > > .tasks = LIST_HEAD_INIT(env.tasks),
> > > };
> > > + int need_unlock = false;
> > >
> > > cpumask_and(cpus, sched_domain_span(sd), cpu_active_mask);
> > >
> > > @@ -11768,6 +11784,13 @@ static int sched_balance_rq(int this_cpu, struct rq *this_rq,
> > > goto out_balanced;
> > > }
> > >
> > > + if (idle != CPU_NEWLY_IDLE && (sd->flags & SD_SERIALIZE)) {
>
> Can you also try removing "idle != CPU_NEWLY_IDLE" and see the workload behavior?
> If workloads don't observe regression, it might be worth serializing it too.
Let me ask my colleague running OLTP to give it a try.
Tim
next prev parent reply other threads:[~2025-11-07 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 23:27 Tim Chen
2025-11-07 2:57 ` K Prateek Nayak
2025-11-07 8:57 ` Shrikanth Hegde
2025-11-07 17:43 ` Tim Chen [this message]
2025-11-10 3:58 ` K Prateek Nayak
2025-11-10 18:19 ` Tim Chen
2025-11-07 17:28 ` Tim Chen
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=4fc95e1409d3218171a54e3baaa2e2a37d724add.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=sshegde@linux.ibm.com \
--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®