From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: K Prateek Nayak <kprateek.nayak@amd.com>
Cc: linux-kernel@vger.kernel.org, juri.lelli@redhat.com,
vschneid@redhat.com, tglx@linutronix.de,
dietmar.eggemann@arm.com, anna-maria@linutronix.de,
frederic@kernel.org, wangyang.guo@intel.com, mingo@kernel.org,
peterz@infradead.org, vincent.guittot@linaro.org
Subject: Re: [PATCH v2 2/3] sched/fair: Change likelyhood of nohz.nr_cpus and do stats update if its due
Date: Tue, 6 Jan 2026 12:14:05 +0530 [thread overview]
Message-ID: <daa3f8c5-47d4-4472-9c35-b7709643f1bd@linux.ibm.com> (raw)
In-Reply-To: <41202126-cf45-46f8-9506-126072bfe0fe@amd.com>
On 1/6/26 11:20 AM, K Prateek Nayak wrote:
> Hello Shrikanth,
>
> On 1/6/2026 9:53 AM, Shrikanth Hegde wrote:
>>> There are also nuances like the smp_mb__after_atomic() in
>>
>> That reminds me, need to upgrade this to smp_mb now, given atomic is gone.
>
> Isn't cpumask_set_cpu() also an atomic op?
>
> set_bit() has a comment stating it is a "relaxed atomic operation" in
> asm-generic/bitops/instrumented-atomic.h which makes it similar to a
> atomic_inc().
"
* set_bit - Atomically set a bit in memory
* @nr: the bit to set
* @addr: the address to start counting from
*
* This is a relaxed atomic operation (no implied memory barriers).
"
I believed the comment. If it was relaxed atomic operation then
one would need a smp barrier.
But it calls arch_set_bit.
Looking at x86 implementation in arch/x86/include/asm/bitops.h it
looks like it does full smp_mb. Whereas on powerpc it doesn't.
So smp_mb__after_atomic can remain as is.
Effective change to v3 is return instead of out.
next prev parent reply other threads:[~2026-01-06 6:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 12:47 [PATCH v2 0/3] sched/fair: improve nohz fields for large systems Shrikanth Hegde
2026-01-02 12:47 ` [PATCH v2 1/3] sched/fair: Move checking for nohz cpus after time check Shrikanth Hegde
2026-01-06 15:50 ` Peter Zijlstra
2026-01-06 15:57 ` Shrikanth Hegde
2026-01-02 12:47 ` [PATCH v2 2/3] sched/fair: Change likelyhood of nohz.nr_cpus and do stats update if its due Shrikanth Hegde
2026-01-05 3:52 ` K Prateek Nayak
2026-01-05 5:07 ` Shrikanth Hegde
2026-01-05 6:41 ` K Prateek Nayak
2026-01-05 10:39 ` Shrikanth Hegde
2026-01-06 3:03 ` K Prateek Nayak
2026-01-06 4:23 ` Shrikanth Hegde
2026-01-06 5:50 ` K Prateek Nayak
2026-01-06 6:44 ` Shrikanth Hegde [this message]
2026-01-02 12:47 ` [PATCH v2 3/3] sched/fair: Remove nohz.nr_cpus and use weight of cpumask instead Shrikanth Hegde
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=daa3f8c5-47d4-4472-9c35-b7709643f1bd@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=anna-maria@linutronix.de \
--cc=dietmar.eggemann@arm.com \
--cc=frederic@kernel.org \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=wangyang.guo@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®