From: "Christoph Lameter (Ampere)" <cl@gentwo.org>
To: Will Deacon <will@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arch@vger.kernel.org
Subject: Re: [PATCH v2] Avoid memory barrier in read_seqcount() through load acquire
Date: Fri, 23 Aug 2024 12:38:05 -0700 (PDT) [thread overview]
Message-ID: <8dcd8772-2c0c-20af-86c4-18f32c07d1e9@gentwo.org> (raw)
In-Reply-To: <20240823103205.GA31866@willie-the-truck>
On Fri, 23 Aug 2024, Will Deacon wrote:
> > +#ifdef CONFIG_ARCH_HAS_ACQUIRE_RELEASE
> > +#define raw_read_seqcount_begin(s) \
> > +({ \
> > + unsigned _seq; \
> > + \
> > + while ((_seq = seqprop_sequence_acquire(s)) & 1) \
> > + cpu_relax(); \
>
> It would also be interesting to see whether smp_cond_load_acquire()
> performs any better that this loop in the !RT case.
The hack to do this follows. Kernel boots but no change in cycles. Also
builds a kernel just fine.
Another benchmark may be better. All my synthetic tests do is run the
function calls in a loop in parallel on multiple cpus.
The main effect here may be the reduction of power since the busyloop is
no longer required. I would favor a solution like this. But the patch is
not clean given the need to get rid of the const attribute with a cast.
Index: linux/include/linux/seqlock.h
===================================================================
--- linux.orig/include/linux/seqlock.h
+++ linux/include/linux/seqlock.h
@@ -325,9 +325,9 @@ SEQCOUNT_LOCKNAME(mutex, struct m
#define raw_read_seqcount_begin(s) \
({ \
unsigned _seq; \
+ seqcount_t *e = seqprop_ptr((struct seqcount_spinlock *)s); \
\
- while ((_seq = seqprop_sequence_acquire(s)) & 1) \
- cpu_relax(); \
+ _seq = smp_cond_load_acquire(&e->sequence, ((e->sequence & 1) == 0)); \
\
kcsan_atomic_next(KCSAN_SEQLOCK_REGION_MAX); \
_seq; \
next prev parent reply other threads:[~2024-08-23 19:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 18:30 Christoph Lameter via B4 Relay
2024-08-23 10:32 ` Will Deacon
2024-08-23 17:56 ` Christoph Lameter (Ampere)
2024-08-23 19:38 ` Christoph Lameter (Ampere) [this message]
2024-08-23 21:05 ` Thomas Gleixner
2024-08-28 17:15 ` Christoph Lameter (Ampere)
2024-09-02 11:55 ` Thomas Gleixner
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=8dcd8772-2c0c-20af-86c4-18f32c07d1e9@gentwo.org \
--to=cl@gentwo.org \
--cc=boqun.feng@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=will@kernel.org \
/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