From: Waiman Long <llong@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>
Cc: linux-kernel@vger.kernel.org, Borislav Petkov <bp@suse.de>,
Ali Saidi <alisaidi@amazon.com>,
Steve Capper <steve.capper@arm.com>
Subject: Re: [PATCH] locking/qrwlock: queued_write_lock_slowpath() cleanup
Date: Mon, 26 Apr 2021 14:51:48 -0400 [thread overview]
Message-ID: <e603e511-6d58-38ea-d936-ed2f4efafc41@redhat.com> (raw)
In-Reply-To: <20210426185017.19815-1-longman@redhat.com>
On 4/26/21 2:50 PM, Waiman Long wrote:
> Make the code more readable by replacing the atomic_cmpxchg_acquire()
> by an equivalent atomic_try_cmpxchg_acquire() and change atomic_add()
> to atomic_or().
>
> For architectures that use qrwlock, I do not find one that has an
> atomic_add() defined but not an atomic_or(). I guess it should be fine
> by changing atomic_add() to atomic_or().
>
> Note that the previous use of atomic_add() isn't wrong as only one
> writer that is the wait_lock owner can set the waiting flag and the
> flag will be cleared later on when acquiring the write lock.
>
> Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
> Signed-off-by: Waiman Long <longman@redhat.com>
> ---
> kernel/locking/qrwlock.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/locking/qrwlock.c b/kernel/locking/qrwlock.c
> index b94f3831e963..ec36b73f4733 100644
> --- a/kernel/locking/qrwlock.c
> +++ b/kernel/locking/qrwlock.c
> @@ -66,12 +66,12 @@ void queued_write_lock_slowpath(struct qrwlock *lock)
> arch_spin_lock(&lock->wait_lock);
>
> /* Try to acquire the lock directly if no reader is present */
> - if (!atomic_read(&lock->cnts) &&
> - (atomic_cmpxchg_acquire(&lock->cnts, 0, _QW_LOCKED) == 0))
> + if (!(cnts = atomic_read(&lock->cnts)) &&
> + atomic_try_cmpxchg_acquire(&lock->cnts, &cnts, _QW_LOCKED))
> goto unlock;
>
> /* Set the waiting flag to notify readers that a writer is pending */
> - atomic_add(_QW_WAITING, &lock->cnts);
> + atomic_or(_QW_WAITING, &lock->cnts);
>
> /* When no more readers or writers, set the locked flag */
> do {
Sorry, I missed the "v2" in the title.
Cheers,
Longman
next prev parent reply other threads:[~2021-04-26 18:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 18:50 Waiman Long
2021-04-26 18:51 ` Waiman Long [this message]
2021-04-27 7:56 ` Will Deacon
2021-05-04 9:19 ` Peter Zijlstra
2021-05-06 13:48 ` [tip: locking/urgent] locking/qrwlock: Cleanup queued_write_lock_slowpath() tip-bot2 for Waiman Long
-- strict thread matches above, loose matches on Subject: below --
2021-04-25 20:06 [PATCH] locking/qrwlock: queued_write_lock_slowpath() cleanup Waiman Long
2021-04-26 8:08 ` Peter Zijlstra
2021-04-26 14:54 ` Waiman Long
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=e603e511-6d58-38ea-d936-ed2f4efafc41@redhat.com \
--to=llong@redhat.com \
--cc=alisaidi@amazon.com \
--cc=boqun.feng@gmail.com \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=steve.capper@arm.com \
--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
all inboxes | Powered by JetHome®