From: Baoquan He <bhe@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@redhat.com, peterz@infradead.org, Waiman.Long@hp.com,
Baoquan He <bhe@redhat.com>
Subject: [PATCH] locking/rwlocks: clean up of qrwlock
Date: Tue, 16 Dec 2014 14:00:40 +0800 [thread overview]
Message-ID: <1418709640-5625-1-git-send-email-bhe@redhat.com> (raw)
In queue_read_lock_slowpath, when writer count becomes 0, we need
increment the read count and get the lock. Then need call
rspin_until_writer_unlock to check again if an incoming writer
steals the lock in the gap. But in rspin_until_writer_unlock
it only checks the writer count, namely low 8 bit of lock->cnts,
no need to subtract the reader count unit specifically. So remove
that subtraction to make it clearer, rspin_until_writer_unlock
just takes the actual lock->cnts as the 2nd argument.
And also change the code comment in queue_write_lock_slowpath to
make it more exact and explicit.
Signed-off-by: Baoquan He <bhe@redhat.com>
---
kernel/locking/qrwlock.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/kernel/locking/qrwlock.c b/kernel/locking/qrwlock.c
index f956ede..ae66c10 100644
--- a/kernel/locking/qrwlock.c
+++ b/kernel/locking/qrwlock.c
@@ -76,7 +76,7 @@ void queue_read_lock_slowpath(struct qrwlock *lock)
while (atomic_read(&lock->cnts) & _QW_WMASK)
cpu_relax_lowlatency();
- cnts = atomic_add_return(_QR_BIAS, &lock->cnts) - _QR_BIAS;
+ cnts = atomic_add_return(_QR_BIAS, &lock->cnts);
rspin_until_writer_unlock(lock, cnts);
/*
@@ -97,14 +97,14 @@ void queue_write_lock_slowpath(struct qrwlock *lock)
/* Put the writer into the wait queue */
arch_spin_lock(&lock->lock);
- /* Try to acquire the lock directly if no reader is present */
+ /* Try to acquire the lock directly if no reader and writer is present */
if (!atomic_read(&lock->cnts) &&
(atomic_cmpxchg(&lock->cnts, 0, _QW_LOCKED) == 0))
goto unlock;
/*
- * Set the waiting flag to notify readers that a writer is pending,
- * or wait for a previous writer to go away.
+ * Wait for a previous writer to go away, then set the waiting flag to
+ * notify readers that a writer is pending.
*/
for (;;) {
cnts = atomic_read(&lock->cnts);
--
1.8.5.3
next reply other threads:[~2014-12-16 6:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 6:00 Baoquan He [this message]
2014-12-16 9:01 ` [PATCH] locking/rwlocks: clean up of qrwlock Peter Zijlstra
2014-12-16 15:36 ` Baoquan He
2014-12-17 21:16 ` Waiman Long
2015-01-06 9:25 ` Baoquan He
2015-01-06 10:13 ` Peter Zijlstra
2015-01-06 12:08 ` Baoquan He
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=1418709640-5625-1-git-send-email-bhe@redhat.com \
--to=bhe@redhat.com \
--cc=Waiman.Long@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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