From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>,
Tim Chen <tim.c.chen@linux.intel.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>
Subject: Re: [RESEND PATCH] sched/fair: Skip sched_balance_running cmpxchg when balance is not due
Date: Wed, 22 Oct 2025 23:12:34 +0530 [thread overview]
Message-ID: <a176acab-caf9-400a-8894-e7c88d684208@linux.ibm.com> (raw)
In-Reply-To: <a5d5ce5e-9f98-4c0d-a4ed-5e4a8a6f7b86@linux.ibm.com>
On 10/16/25 7:33 PM, Shrikanth Hegde wrote:
>
>
> On 10/14/25 3:12 PM, Peter Zijlstra wrote:
>> On Tue, Oct 14, 2025 at 03:03:41PM +0530, Shrikanth Hegde wrote:
>>
>>>> @@ -11758,6 +11775,12 @@ static int sched_balance_rq(int this_cpu,
>>>> struct rq *this_rq,
>>>> goto out_balanced;
>>>> }
>>>> + if (idle != CPU_NEWLY_IDLE && (sd->flags & SD_SERIALIZE)) {
>>>> + if (atomic_cmpxchg_acquire(&sched_balance_running, 0, 1))
>>>> + goto out_balanced;
>>>
>>> Maybe goto out instead of out_balanced ?
>>
>> That would be inconsistent with the !should_we_balance() goto
>> out_balanced right above this, no?
>>
> Hi Peter.
>
> Did similar probe points numbers compared to this. Even the patch is
> quite similar to what
> was suggested there a while ago.
> https://lore.kernel.org/all/41e11090-a100-48a7-a0dd-
> c989772822d7@linux.ibm.com/
>
> 480 CPUs system with 6 NUMA nodes. (different system than last time)
>
Hi Peter, Tim.
How are we proceeding here? Should i send the below patch with changelog or
is it being worked out by either of you.
It is really beneficial for large systems to avoid un-neccessary cache bouncing.
> tl;dr
>
> - Number of time sched_balance_running is taken is way less after the
> swb check. (which is great)
> - Number of time it fails to set is very low after swb. (So out_balanced
> vs out may not make a
> significant difference.)
> - Patch is at the end. It is this patch + redo stuff +
> (ref_variable_stuff(ignore))
>
>
next prev parent reply other threads:[~2025-10-22 17:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 23:00 [RESEND PATCH] sched/fair: Skip sched_balance_running cmpxchg when balance is not due Tim Chen
2025-10-03 5:23 ` Shrikanth Hegde
2025-10-03 16:37 ` Tim Chen
2025-10-13 14:26 ` Peter Zijlstra
2025-10-13 16:32 ` Chen, Yu C
2025-10-13 16:41 ` Shrikanth Hegde
2025-10-13 16:43 ` Chen, Yu C
2025-10-14 9:26 ` Peter Zijlstra
2025-10-13 21:54 ` Tim Chen
2025-10-14 9:24 ` Peter Zijlstra
2025-10-14 9:33 ` Shrikanth Hegde
2025-10-14 9:42 ` Peter Zijlstra
2025-10-14 9:51 ` Shrikanth Hegde
2025-10-16 14:03 ` Shrikanth Hegde
2025-10-22 17:42 ` Shrikanth Hegde [this message]
2025-10-14 13:50 ` Srikar Dronamraju
2025-10-14 13:59 ` Peter Zijlstra
2025-10-14 14:28 ` Shrikanth Hegde
2025-10-14 18:05 ` 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=a176acab-caf9-400a-8894-e7c88d684208@linux.ibm.com \
--to=sshegde@linux.ibm.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=tim.c.chen@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.