From: Jason Low <jason.low2@hp.com>
To: mingo@kernel.org, peterz@infradead.org, tglx@linutronix.de,
akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, paulmck@linux.vnet.ibm.com,
tim.c.chen@linux.intel.com, peter@hurleysoftware.com,
riel@redhat.com, hpa@zytor.com, walken@google.com,
davidlohr@hp.com, Waiman.Long@hp.com, aswin@hp.com,
scott.norton@hp.com, chegu_vinod@hp.com, jason.low2@hp.com
Subject: [RFC PATCH 3/3] locking/mutex: Optimize mutex trylock slowpath
Date: Wed, 4 Jun 2014 12:08:31 -0700 [thread overview]
Message-ID: <1401908911-8947-4-git-send-email-jason.low2@hp.com> (raw)
In-Reply-To: <1401908911-8947-1-git-send-email-jason.low2@hp.com>
In __mutex_trylock_slowpath(), we acquire the wait_lock spinlock,
xchg() lock->count with -1, then set lock->count back to 0 if there
are no waiters, and return true if the prev lock count was 1.
However, if we the mutex is already locked, then there may not be
much point in attempting the above operations. In this patch, we only
attempt the above operations if the mutex is unlocked.
The new MUTEX_IS_UNLOCKED() macro is also used for this.
Signed-off-by: Jason Low <jason.low2@hp.com>
---
kernel/locking/mutex.c | 27 ++++++++++++++++-----------
1 files changed, 16 insertions(+), 11 deletions(-)
diff --git a/kernel/locking/mutex.c b/kernel/locking/mutex.c
index fc55f72..c65680d 100644
--- a/kernel/locking/mutex.c
+++ b/kernel/locking/mutex.c
@@ -821,21 +821,26 @@ static inline int __mutex_trylock_slowpath(atomic_t *lock_count)
{
struct mutex *lock = container_of(lock_count, struct mutex, count);
unsigned long flags;
- int prev;
+ int prev = 0;
- spin_lock_mutex(&lock->wait_lock, flags);
+ /*
+ * Only need to trylock the mutex if it is unlocked.
+ */
+ if (MUTEX_IS_UNLOCKED(lock)) {
+ spin_lock_mutex(&lock->wait_lock, flags);
- prev = atomic_xchg(&lock->count, -1);
- if (likely(prev == 1)) {
- mutex_set_owner(lock);
- mutex_acquire(&lock->dep_map, 0, 1, _RET_IP_);
- }
+ prev = atomic_xchg(&lock->count, -1);
+ if (likely(prev == 1)) {
+ mutex_set_owner(lock);
+ mutex_acquire(&lock->dep_map, 0, 1, _RET_IP_);
+ }
- /* Set it back to 0 if there are no waiters: */
- if (likely(list_empty(&lock->wait_list)))
- atomic_set(&lock->count, 0);
+ /* Set it back to 0 if there are no waiters: */
+ if (likely(list_empty(&lock->wait_list)))
+ atomic_set(&lock->count, 0);
- spin_unlock_mutex(&lock->wait_lock, flags);
+ spin_unlock_mutex(&lock->wait_lock, flags);
+ }
return prev == 1;
}
--
1.7.1
next prev parent reply other threads:[~2014-06-04 19:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 19:08 [RFC PATCH 0/3] locking/mutex: Modifications to mutex Jason Low
2014-06-04 19:08 ` [RFC PATCH 1/3] locking/mutex: Try to acquire mutex only if it is unlocked Jason Low
2014-06-04 19:43 ` Peter Zijlstra
2014-06-04 20:57 ` Davidlohr Bueso
2014-06-04 20:58 ` Davidlohr Bueso
2014-06-09 17:38 ` Jason Low
2014-06-11 21:00 ` Long, Wai Man
2014-06-11 21:48 ` Jason Low
2014-06-12 1:25 ` Long, Wai Man
2014-06-04 21:53 ` Jason Low
2014-06-04 21:26 ` Jason Low
2014-06-04 21:54 ` Thomas Gleixner
2014-06-04 22:13 ` Jason Low
2014-06-05 3:24 ` Waiman Long
2014-06-05 19:21 ` Jason Low
2014-06-04 19:08 ` [RFC PATCH 2/3] locking/mutex: Correct documentation on mutex optimistic spinning Jason Low
2014-06-04 20:11 ` Davidlohr Bueso
2014-06-04 20:30 ` Jason Low
2014-06-04 19:08 ` Jason Low [this message]
2014-06-04 20:28 ` [RFC PATCH 3/3] locking/mutex: Optimize mutex trylock slowpath Davidlohr Bueso
2014-06-04 21:47 ` Jason Low
2014-06-05 1:10 ` Davidlohr Bueso
2014-06-05 3:08 ` Jason Low
2014-06-04 20:13 ` [RFC PATCH 0/3] locking/mutex: Modifications to mutex Davidlohr Bueso
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=1401908911-8947-4-git-send-email-jason.low2@hp.com \
--to=jason.low2@hp.com \
--cc=Waiman.Long@hp.com \
--cc=akpm@linux-foundation.org \
--cc=aswin@hp.com \
--cc=chegu_vinod@hp.com \
--cc=davidlohr@hp.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peter@hurleysoftware.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=scott.norton@hp.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=walken@google.com \
/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
Powered by JetHome