From: tip-bot for Waiman Long <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: doug.hatch@hpe.com, linux-kernel@vger.kernel.org,
jason.low2@hp.com, akpm@linux-foundation.org,
Waiman.Long@hpe.com, paulmck@linux.vnet.ibm.com,
scott.norton@hpe.com, david@fromorbit.com, tglx@linutronix.de,
mingo@kernel.org, peterz@infradead.org, dave@stgolabs.net,
torvalds@linux-foundation.org, peter@hurleysoftware.com,
hpa@zytor.com
Subject: [tip:locking/core] locking/rwsem: Improve reader wakeup code
Date: Wed, 8 Jun 2016 07:25:55 -0700 [thread overview]
Message-ID: <tip-bf7b4c472db44413251bcef79ca1f6bf1ec81475@git.kernel.org> (raw)
In-Reply-To: <1463534783-38814-5-git-send-email-Waiman.Long@hpe.com>
Commit-ID: bf7b4c472db44413251bcef79ca1f6bf1ec81475
Gitweb: http://git.kernel.org/tip/bf7b4c472db44413251bcef79ca1f6bf1ec81475
Author: Waiman Long <Waiman.Long@hpe.com>
AuthorDate: Tue, 17 May 2016 21:26:22 -0400
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Wed, 8 Jun 2016 15:17:00 +0200
locking/rwsem: Improve reader wakeup code
In __rwsem_do_wake(), the reader wakeup code will assume a writer
has stolen the lock if the active reader/writer count is not 0.
However, this is not as reliable an indicator as the original
"< RWSEM_WAITING_BIAS" check. If another reader is present, the code
will still break out and exit even if the writer is gone. This patch
changes it to check the same "< RWSEM_WAITING_BIAS" condition to
reduce the chance of false positive.
Signed-off-by: Waiman Long <Waiman.Long@hpe.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Peter Hurley <peter@hurleysoftware.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Dave Chinner <david@fromorbit.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>
Cc: Douglas Hatch <doug.hatch@hpe.com>
Cc: Jason Low <jason.low2@hp.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Scott J Norton <scott.norton@hpe.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Link: http://lkml.kernel.org/r/1463534783-38814-5-git-send-email-Waiman.Long@hpe.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
kernel/locking/rwsem-xadd.c | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/kernel/locking/rwsem-xadd.c b/kernel/locking/rwsem-xadd.c
index 6b0d060..4f1daf5 100644
--- a/kernel/locking/rwsem-xadd.c
+++ b/kernel/locking/rwsem-xadd.c
@@ -156,9 +156,14 @@ __rwsem_mark_wake(struct rw_semaphore *sem,
oldcount = atomic_long_add_return(adjustment, &sem->count) - adjustment;
if (unlikely(oldcount < RWSEM_WAITING_BIAS)) {
- /* A writer stole the lock. Undo our reader grant. */
- if (atomic_long_sub_return(adjustment, &sem->count) &
- RWSEM_ACTIVE_MASK)
+ /*
+ * If the count is still less than RWSEM_WAITING_BIAS
+ * after removing the adjustment, it is assumed that
+ * a writer has stolen the lock. We have to undo our
+ * reader grant.
+ */
+ if (atomic_long_add_return(-adjustment, &sem->count) <
+ RWSEM_WAITING_BIAS)
goto out;
/* Last active locker left. Retry waking readers. */
goto try_reader_grant;
next prev parent reply other threads:[~2016-06-08 14:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 1:26 [PATCH v4 0/5] [PATCH v3 0/4] locking/rwsem: Add reader-owned state to the owner field Waiman Long
2016-05-18 1:26 ` [PATCH v4 1/5] " Waiman Long
2016-06-06 17:18 ` Davidlohr Bueso
2016-06-06 20:03 ` Waiman Long
2016-06-06 21:02 ` Peter Zijlstra
2016-06-06 21:49 ` Waiman Long
2016-06-08 14:25 ` [tip:locking/core] " tip-bot for Waiman Long
2016-05-18 1:26 ` [PATCH v4 2/5] locking/rwsem: Protect all writes to owner by WRITE_ONCE() Waiman Long
2016-05-18 14:04 ` Davidlohr Bueso
2016-05-18 17:21 ` [PATCH v4 2/5] locking/rwsem: Protect all writes to owner by WRITE_ONCE Jason Low
2016-05-18 18:29 ` Waiman Long
2016-05-18 19:58 ` Jason Low
2016-05-19 22:21 ` Jason Low
2016-05-20 20:26 ` Waiman Long
2016-05-21 16:04 ` Peter Hurley
2016-05-22 10:42 ` Peter Zijlstra
2016-05-23 18:46 ` Jason Low
2016-05-23 19:44 ` Davidlohr Bueso
2016-05-23 20:15 ` Paul E. McKenney
2016-05-23 21:04 ` Davidlohr Bueso
2016-05-25 1:25 ` Waiman Long
2016-05-18 17:23 ` [PATCH v4 2/5] locking/rwsem: Protect all writes to owner by WRITE_ONCE() Jason Low
2016-06-08 14:25 ` [tip:locking/core] " tip-bot for Waiman Long
2016-05-18 1:26 ` [PATCH v4 3/5] locking/rwsem: Don't wake up one's own task Waiman Long
2016-05-18 10:30 ` Peter Zijlstra
2016-05-18 16:04 ` Waiman Long
2016-05-18 1:26 ` [PATCH v4 4/5] locking/rwsem: Improve reader wakeup code Waiman Long
2016-06-08 14:25 ` tip-bot for Waiman Long [this message]
2016-05-18 1:26 ` [PATCH v4 5/5] locking/rwsem: Streamline the rwsem_optimistic_spin() code Waiman Long
2016-06-08 14:26 ` [tip:locking/core] " tip-bot for Waiman Long
2016-05-18 10:52 ` [PATCH v4 0/5] [PATCH v3 0/4] locking/rwsem: Add reader-owned state to the owner field Peter Zijlstra
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=tip-bf7b4c472db44413251bcef79ca1f6bf1ec81475@git.kernel.org \
--to=tipbot@zytor.com \
--cc=Waiman.Long@hpe.com \
--cc=akpm@linux-foundation.org \
--cc=dave@stgolabs.net \
--cc=david@fromorbit.com \
--cc=doug.hatch@hpe.com \
--cc=hpa@zytor.com \
--cc=jason.low2@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peter@hurleysoftware.com \
--cc=peterz@infradead.org \
--cc=scott.norton@hpe.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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