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 0/3] locking/rtmutex: Another crack at spin on owner
Date: Tue, 8 Mar 2016 10:20:20 -0800 [thread overview]
Message-ID: <1457461223-4301-1-git-send-email-dave@stgolabs.net> (raw)
Hi,
This is a (painfully late) followup to proposal sometime ago to add
spin on owner to rtmutexes. My first attempt was rather liberal 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 (3):
rtmutex: Delete save_state member of struct rt_mutex
rtmutex: Add rt_mutex_init_waiter helper
rtmutex: Reduce top-waiter blocking on a lock
include/linux/rtmutex.h | 1 -
kernel/Kconfig.locks | 4 ++
kernel/futex.c | 5 +--
kernel/locking/rtmutex.c | 82 +++++++++++++++++++++++++++++++++++------
kernel/locking/rtmutex_common.h | 17 ++++++++-
5 files changed, 92 insertions(+), 17 deletions(-)
--
2.1.4
next reply other threads:[~2016-03-08 18:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 18:20 Davidlohr Bueso [this message]
2016-03-08 18:20 ` [PATCH 1/3] rtmutex: Delete save_state member of struct rt_mutex Davidlohr Bueso
2016-03-08 18:20 ` [PATCH 2/3] rtmutex: Add rt_mutex_init_waiter helper Davidlohr Bueso
2016-03-14 13:16 ` Peter Zijlstra
2016-03-08 18:20 ` [PATCH 3/3] rtmutex: Reduce top-waiter blocking on a lock Davidlohr Bueso
2016-03-14 13:23 ` Peter Zijlstra
2016-03-08 22:05 ` [PATCH 4/3] rtmutex: Avoid barrier in rt_mutex_handle_deadlock Davidlohr Bueso
2016-03-14 13:40 ` Peter Zijlstra
2016-03-21 18:16 ` Davidlohr Bueso
2016-03-22 10:21 ` Peter Zijlstra
2016-03-22 11:32 ` Heiko Carstens
2016-03-22 12:20 ` Peter Zijlstra
2016-03-22 13:26 ` Heiko Carstens
2016-03-22 13:55 ` Peter Zijlstra
2016-03-22 14:45 ` Heiko Carstens
2016-03-22 16:41 ` Peter Zijlstra
2016-03-22 21:46 ` Heiko Carstens
2016-03-25 2:30 ` 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=1457461223-4301-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;
as well as URLs for NNTP newsgroup(s).