From: Peter Zijlstra <peterz@infradead.org> To: Boqun Feng <boqun.feng@gmail.com> Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@kernel.org>, Juri Lelli <juri.lelli@redhat.com>, Steven Rostedt <rostedt@goodmis.org>, Davidlohr Bueso <dave@stgolabs.net>, Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>, Sebastian Andrzej Siewior <bigeasy@linutronix.de>, Mike Galbraith <efault@gmx.de>, Daniel Bristot de Oliveira <bristot@redhat.com>, LKML <linux-kernel@vger.kernel.org> Subject: Re: [RFC] locking: rwbase: Take care of ordering guarantee for fastpath reader Date: Wed, 8 Sep 2021 13:51:24 +0200 [thread overview] Message-ID: <YTijvI3BpBxkWcTd@hirez.programming.kicks-ass.net> (raw) In-Reply-To: <20210901150627.620830-1-boqun.feng@gmail.com> On Wed, Sep 01, 2021 at 11:06:27PM +0800, Boqun Feng wrote: > Readers of rwbase can lock and unlock without taking any inner lock, if > that happens, we need the ordering provided by atomic operations to > satisfy the ordering semantics of lock/unlock. Without that, considering > the follow case: > > { X = 0 initially } > > CPU 0 CPU 1 > ===== ===== > rt_write_lock(); > X = 1 > rt_write_unlock(): > atomic_add(READER_BIAS - WRITER_BIAS, ->readers); > // ->readers is READER_BIAS. > rt_read_lock(): > if ((r = atomic_read(->readers)) < 0) // True > atomic_try_cmpxchg(->readers, r, r + 1); // succeed. > <acquire the read lock via fast path> > > r1 = X; // r1 may be 0, because nothing prevent the reordering > // of "X=1" and atomic_add() on CPU 1. > > Therefore audit every usage of atomic operations that may happen in a > fast path, and add necessary barriers. > > Signed-off-by: Boqun Feng <boqun.feng@gmail.com> > --- Does this work for you? diff --git a/kernel/locking/rwbase_rt.c b/kernel/locking/rwbase_rt.c index 4ba15088e640..4685d3780683 100644 --- a/kernel/locking/rwbase_rt.c +++ b/kernel/locking/rwbase_rt.c @@ -53,6 +53,7 @@ static __always_inline int rwbase_read_trylock(struct rwbase_rt *rwb) * set. */ for (r = atomic_read(&rwb->readers); r < 0;) { + /* Fully ordered on success, provides ACQUIRE */ if (likely(atomic_try_cmpxchg(&rwb->readers, &r, r + 1))) return 1; } @@ -162,6 +163,8 @@ static __always_inline void rwbase_read_unlock(struct rwbase_rt *rwb, /* * rwb->readers can only hit 0 when a writer is waiting for the * active readers to leave the critical section. + * + * Fully ordered, provides RELEASE. */ if (unlikely(atomic_dec_and_test(&rwb->readers))) __rwbase_read_unlock(rwb, state); @@ -172,7 +175,10 @@ static inline void __rwbase_write_unlock(struct rwbase_rt *rwb, int bias, { struct rt_mutex_base *rtm = &rwb->rtmutex; - atomic_add(READER_BIAS - bias, &rwb->readers); + /* + * Needs to provide RELEASE vs rwbase_read_trylock(). + */ + (void)atomic_fetch_add_release(READER_BIAS - bias, &rwb->readers); raw_spin_unlock_irqrestore(&rtm->wait_lock, flags); rwbase_rtmutex_unlock(rtm); } @@ -201,23 +207,30 @@ static int __sched rwbase_write_lock(struct rwbase_rt *rwb, { struct rt_mutex_base *rtm = &rwb->rtmutex; unsigned long flags; + int readers; /* Take the rtmutex as a first step */ if (rwbase_rtmutex_lock_state(rtm, state)) return -EINTR; /* Force readers into slow path */ - atomic_sub(READER_BIAS, &rwb->readers); + readers = atomic_sub_return_relaxed(READER_BIAS, &rwb->readers); - raw_spin_lock_irqsave(&rtm->wait_lock, flags); /* * set_current_state() for rw_semaphore * current_save_and_set_rtlock_wait_state() for rwlock */ rwbase_set_and_save_current_state(state); + raw_spin_lock_irqsave(&rtm->wait_lock, flags); - /* Block until all readers have left the critical section. */ - for (; atomic_read(&rwb->readers);) { + /* + * Block until all readers have left the critical section. + * + * In the case of !readers, the above implies TSO ordering + * at the very least and hence provides ACQUIRE vs the earlier + * atomic_sub_return_relaxed(). + */ + while (readers) { /* Optimized out for rwlocks */ if (rwbase_signal_pending_state(state, current)) { __set_current_state(TASK_RUNNING); @@ -230,8 +243,12 @@ static int __sched rwbase_write_lock(struct rwbase_rt *rwb, * Schedule and wait for the readers to leave the critical * section. The last reader leaving it wakes the waiter. */ - if (atomic_read(&rwb->readers) != 0) + readers = atomic_read(&rwb->readers); + if (readers != 0) rwbase_schedule(); + /* + * Implies smp_mb() and provides ACQUIRE for the !readers case. + */ set_current_state(state); raw_spin_lock_irqsave(&rtm->wait_lock, flags); } @@ -253,7 +270,10 @@ static inline int rwbase_write_trylock(struct rwbase_rt *rwb) atomic_sub(READER_BIAS, &rwb->readers); raw_spin_lock_irqsave(&rtm->wait_lock, flags); - if (!atomic_read(&rwb->readers)) { + /* + * Needs ACQUIRE vs rwbase_read_unlock(); + */ + if (!atomic_read_acquire(&rwb->readers)) { atomic_set(&rwb->readers, WRITER_BIAS); raw_spin_unlock_irqrestore(&rtm->wait_lock, flags); return 1;
next prev parent reply other threads:[~2021-09-08 11:52 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-01 15:06 Boqun Feng 2021-09-01 18:53 ` Waiman Long 2021-09-01 20:22 ` Davidlohr Bueso 2021-09-02 5:02 ` Boqun Feng 2021-09-02 11:55 ` Peter Zijlstra 2021-09-03 14:50 ` Boqun Feng 2021-09-04 10:12 ` Peter Zijlstra 2021-09-04 10:14 ` Peter Zijlstra 2021-09-04 10:19 ` Boqun Feng 2021-09-08 11:51 ` Peter Zijlstra [this message] 2021-09-08 12:14 ` Peter Zijlstra 2021-09-08 13:00 ` Boqun Feng 2021-09-08 13:08 ` Boqun Feng 2021-09-08 14:41 ` Peter Zijlstra 2021-09-08 14:49 ` Peter Zijlstra 2021-09-08 18:34 ` Davidlohr Bueso 2021-09-08 13:27 ` Boqun Feng
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=YTijvI3BpBxkWcTd@hirez.programming.kicks-ass.net \ --to=peterz@infradead.org \ --cc=bigeasy@linutronix.de \ --cc=boqun.feng@gmail.com \ --cc=bristot@redhat.com \ --cc=dave@stgolabs.net \ --cc=efault@gmx.de \ --cc=juri.lelli@redhat.com \ --cc=linux-kernel@vger.kernel.org \ --cc=longman@redhat.com \ --cc=mingo@kernel.org \ --cc=rostedt@goodmis.org \ --cc=tglx@linutronix.de \ --cc=will@kernel.org \ --subject='Re: [RFC] locking: rwbase: Take care of ordering guarantee for fastpath reader' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).