From: Davidlohr Bueso <dave@stgolabs.net>
To: tglx@linutronix.de, mingo@kernel.org
Cc: peterz@infradead.org, bigeasy@linutronix.de,
umgwanakikbuti@gmail.com, paulmck@linux.vnet.ibm.com,
dave@stgolabs.net, linux-kernel@vger.kernel.org
Subject: [PATCH -tip v2 0/4] rtmutex: Another crack at spin on owner
Date: Sun, 3 Apr 2016 23:32:42 -0700 [thread overview]
Message-ID: <1459751566-31872-1-git-send-email-dave@stgolabs.net> (raw)
Changes from v1:
- Dropped patch 4 that removed the barrier in the deadlock path.
- Added patch 2 (trivial) to use poison.h defines.
- sprinkled READ/WRITE_ONCE around lock->owner, even if updated
inside the cr. (peterz)
- More testing time.
This is a followup to proposal sometime ago to add spin on owner to rtmutexes.
My first attempt was rather permissive in that I tried avoiding the pi
dance and let the lock be stolen. However, due to -rt constraints this
series only deals with top-waiter, based on what we do in the preempt
rt patchset.
First two patches are trivial and the whole patchset as survived a week
of locktorture+pi_stress pounding at the same time without anything
breaking. That said, I'm sure it needs more testing and eyeballs, these
paths make my head hurt.
Thanks!
Davidlohr Bueso (4):
rtmutex: Delete save_state member of struct rt_mutex
rtmutex: Use waiter debug init,free magic numbers
rtmutex: Add rt_mutex_init_waiter helper
rtmutex: Reduce top-waiter blocking on a lock
include/linux/poison.h | 4 +-
include/linux/rtmutex.h | 3 +-
kernel/Kconfig.locks | 4 ++
kernel/futex.c | 5 +--
kernel/locking/mutex-debug.c | 4 +-
kernel/locking/rtmutex-debug.c | 4 +-
kernel/locking/rtmutex.c | 88 ++++++++++++++++++++++++++++++++++-------
kernel/locking/rtmutex_common.h | 17 +++++++-
8 files changed, 102 insertions(+), 27 deletions(-)
--
2.7.4
next reply other threads:[~2016-04-04 6:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 6:32 Davidlohr Bueso [this message]
2016-04-04 6:32 ` [PATCH 1/4] rtmutex: Delete save_state member of struct rt_mutex Davidlohr Bueso
2016-04-04 6:32 ` [PATCH 2/4] rtmutex: Use waiter debug init,free magic numbers Davidlohr Bueso
2016-04-04 6:32 ` [PATCH 3/4] rtmutex: Add rt_mutex_init_waiter helper Davidlohr Bueso
2016-04-04 6:32 ` [PATCH 4/4] rtmutex: Reduce top-waiter blocking on a lock Davidlohr Bueso
2016-04-28 17:34 ` [PATCH -tip v2 0/4] rtmutex: Another crack at spin on owner 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=1459751566-31872-1-git-send-email-dave@stgolabs.net \
--to=dave@stgolabs.net \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=umgwanakikbuti@gmail.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
all inboxes | Powered by JetHome®