LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@kernel.org>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Jason Low <jason.low2@hp.com>,
Michel Lespinasse <walken@google.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
linux-kernel@vger.kernel.org, Davidlohr Bueso <dave@stgolabs.net>
Subject: [PATCH -tip 0/6] rwsem: Fine tuning
Date: Sun, 25 Jan 2015 23:36:03 -0800 [thread overview]
Message-ID: <1422257769-14083-1-git-send-email-dave@stgolabs.net> (raw)
Hello,
First two patches are self descriptive obvious add-ons.
The rest are performance enhancements for write-mostly workloads.
While this is not our priority (use mutexes instead!!), there are
cases where heavy use of writers can severly hurt rwsem performance.
For instace, we got reports[1] of writer only issues when converting
the i_mmap_rwsem from mutex, on a workload that pathologically pounds
on this lock for vma operations:
- 81.20% execl [kernel.kallsyms] [k] osq_lock
- 100.00% mutex_optimistic_spin
__mutex_lock_slowpath
- mutex_lock
+ 47.71% unlink_file_vma
+ 34.91% vma_adjust
+ 17.38% vma_link
This is enough to make small differences painfully evident. These changes
(particularly patch 6/6) recover most (~75%) of the performance regression.
Patches 4 and 6 deal with optimistic spinning fine tunning, while patch
5 is an attempt to get tid of two barriers when blocking. While I believe
this is safe, it certainly needs more eyeballs, I could have easily overlooked
something. Most of these changes are straighforward, but have various implications.
Passes multiple x86-64 tests.
Thanks!
[1] https://lkml.org/lkml/2015/1/7/884
Davidlohr Bueso (6):
locking/rwsem: Use task->state helpers
locking/rwsem: Document barrier need when waking tasks
locking/rwsem: Set lock ownership ASAP
locking/rwsem: Avoid deceiving lock spinners
locking/rwsem: Optimize slowpath/sleeping
locking/rwsem: Check for active lock before bailing on spinning
kernel/locking/mutex.c | 2 +-
kernel/locking/rwsem-spinlock.c | 7 +++-
kernel/locking/rwsem-xadd.c | 71 +++++++++++++++++++++++++++++------------
kernel/locking/rwsem.c | 22 +------------
kernel/locking/rwsem.h | 20 ++++++++++++
5 files changed, 78 insertions(+), 44 deletions(-)
create mode 100644 kernel/locking/rwsem.h
--
2.1.2
next reply other threads:[~2015-01-26 7:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 7:36 Davidlohr Bueso [this message]
2015-01-26 7:36 ` [PATCH 1/6] locking/rwsem: Use task->state helpers Davidlohr Bueso
2015-02-04 14:38 ` [tip:locking/core] " tip-bot for Davidlohr Bueso
2015-01-26 7:36 ` [PATCH 2/6] locking/rwsem: Document barrier need when waking tasks Davidlohr Bueso
2015-01-27 17:07 ` Peter Zijlstra
2015-01-27 20:30 ` Davidlohr Bueso
2015-01-26 7:36 ` [PATCH 3/6] locking/rwsem: Set lock ownership ASAP Davidlohr Bueso
2015-01-27 17:10 ` Peter Zijlstra
2015-01-27 19:18 ` Davidlohr Bueso
2015-01-26 7:36 ` [PATCH 4/6] locking/rwsem: Avoid deceiving lock spinners Davidlohr Bueso
2015-01-27 17:23 ` Jason Low
2015-01-28 3:54 ` Davidlohr Bueso
2015-01-28 17:01 ` Tim Chen
2015-01-28 21:03 ` Jason Low
2015-01-29 1:10 ` Davidlohr Bueso
2015-01-29 20:13 ` Jason Low
2015-01-29 20:18 ` Jason Low
2015-01-29 23:15 ` Davidlohr Bueso
2015-01-30 1:52 ` Refactoring mutex spin on owner code Jason Low
2015-01-30 7:14 ` Davidlohr Bueso
2015-01-30 7:51 ` Peter Zijlstra
2015-01-26 7:36 ` [PATCH 5/6] locking/rwsem: Optimize slowpath/sleeping Davidlohr Bueso
2015-01-27 17:34 ` Peter Zijlstra
2015-01-27 21:57 ` Davidlohr Bueso
2015-01-26 7:36 ` [PATCH 6/6] locking/rwsem: Check for active lock before bailing on spinning Davidlohr Bueso
2015-01-27 18:11 ` Jason Low
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=1422257769-14083-1-git-send-email-dave@stgolabs.net \
--to=dave@stgolabs.net \
--cc=jason.low2@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tim.c.chen@linux.intel.com \
--cc=walken@google.com \
--subject='Re: [PATCH -tip 0/6] rwsem: Fine tuning' \
/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).