From: Peter Zijlstra <peterz@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Waiman Long <waiman.long@hpe.com>, Jason Low <jason.low2@hpe.com>,
Ding Tianhong <dingtianhong@huawei.com>,
Thomas Gleixner <tglx@linutronix.de>,
Will Deacon <Will.Deacon@arm.com>, Ingo Molnar <mingo@redhat.com>,
Imre Deak <imre.deak@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Tim Chen <tim.c.chen@linux.intel.com>,
Terry Rudd <terry.rudd@hpe.com>,
"Paul E. McKenney" <paulmck@us.ibm.com>,
Jason Low <jason.low2@hp.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: [PATCH -v3 07/10] mutex: Restructure wait loop
Date: Mon, 05 Sep 2016 14:36:43 +0200 [thread overview]
Message-ID: <20160905124027.619747346@infradead.org> (raw)
In-Reply-To: <20160905123636.450529224@infradead.org>
[-- Attachment #1: peterz-locking-mutex-wait_lock-opt.patch --]
[-- Type: text/plain, Size: 2257 bytes --]
Doesn't really matter yet, but pull the HANDOFF and trylock out from
under the wait_lock.
The intention is to add an optimistic spin loop here, which requires
we do not hold the wait_lock, so shuffle code around in preparation.
Also clarify the purpose of taking the wait_lock in the wait loop, its
tempting to want to avoid it altogether, but the cancellation cases
need to to avoid loosing wakeups.
Suggested-by: Waiman Long <waiman.long@hpe.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/locking/mutex.c | 18 ++++++++++++++----
1 file changed, 14 insertions(+), 4 deletions(-)
--- a/kernel/locking/mutex.c
+++ b/kernel/locking/mutex.c
@@ -627,10 +627,12 @@ __mutex_lock_common(struct mutex *lock,
lock_contended(&lock->dep_map, ip);
+ set_task_state(task, state);
for (;;) {
/*
- * got a signal? (This code gets eliminated in the
- * TASK_UNINTERRUPTIBLE case.)
+ * Check for signals and wound conditions while holding
+ * wait_lock. This ensures the lock cancellation is ordered
+ * against mutex_unlock() and wake-ups do not go missing.
*/
if (unlikely(signal_pending_state(state, task))) {
ret = -EINTR;
@@ -643,20 +645,27 @@ __mutex_lock_common(struct mutex *lock,
goto err;
}
- __set_task_state(task, state);
spin_unlock_mutex(&lock->wait_lock, flags);
schedule_preempt_disabled();
- spin_lock_mutex(&lock->wait_lock, flags);
if (__mutex_waiter_is_first(lock, &waiter)) {
first = true;
__mutex_set_flag(lock, MUTEX_FLAG_HANDOFF);
}
+ set_task_state(task, state);
+ /*
+ * Here we order against unlock; we must either see it change
+ * state back to RUNNING and fall through the next schedule(),
+ * or we must see its unlock and acquire.
+ */
if (__mutex_trylock(lock, true))
break;
+
+ spin_lock_mutex(&lock->wait_lock, flags);
}
__set_task_state(task, TASK_RUNNING);
+ spin_lock_mutex(&lock->wait_lock, flags);
remove_waiter:
mutex_remove_waiter(lock, &waiter, task);
@@ -681,6 +690,7 @@ __mutex_lock_common(struct mutex *lock,
return 0;
err:
+ __set_task_state(task, TASK_RUNNING);
mutex_remove_waiter(lock, &waiter, task);
spin_unlock_mutex(&lock->wait_lock, flags);
debug_mutex_free_waiter(&waiter);
next prev parent reply other threads:[~2016-09-05 12:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 12:36 [PATCH -v3 00/10] locking/mutex: Rewrite basic mutex Peter Zijlstra
2016-09-05 12:36 ` [PATCH -v3 01/10] locking/drm: Kill mutex trickery Peter Zijlstra
2016-09-05 12:36 ` [PATCH -v3 02/10] sh/atomic: Fix ATOMIC_FETCH_OP() Peter Zijlstra
2016-09-05 12:36 ` [PATCH -v3 03/10] locking/mutex: Rework mutex::owner Peter Zijlstra
2016-09-05 12:36 ` [PATCH -v3 04/10] locking/mutex: Kill arch specific code Peter Zijlstra
2016-09-05 12:36 ` [PATCH -v3 05/10] locking/mutex: Allow MUTEX_SPIN_ON_OWNER when DEBUG_MUTEXES Peter Zijlstra
2016-09-05 12:36 ` [PATCH -v3 06/10] locking/mutex: Add lock handoff to avoid starvation Peter Zijlstra
2016-09-05 12:36 ` Peter Zijlstra [this message]
[not found] ` <57D31A3B.7000105@hpe.com>
[not found] ` <57D31C67.8010809@hpe.com>
2016-09-14 10:33 ` [PATCH -v3 07/10] mutex: Restructure wait loop Peter Zijlstra
2016-09-05 12:36 ` [PATCH -v3 08/10] locking/mutex: Simplify some ww_mutex code in __mutex_lock_common() Peter Zijlstra
2016-09-05 12:36 ` [PATCH -v3 09/10] locking/mutex: Enable optimistic spinning of woken waiter Peter Zijlstra
2016-09-05 12:36 ` [RFC][PATCH -v3 10/10] locking/mutex: Implement alternative HANDOFF Peter Zijlstra
2016-09-09 22:32 ` Waiman Long
2016-09-12 15:20 ` 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=20160905124027.619747346@infradead.org \
--to=peterz@infradead.org \
--cc=Will.Deacon@arm.com \
--cc=dave@stgolabs.net \
--cc=dingtianhong@huawei.com \
--cc=imre.deak@intel.com \
--cc=jason.low2@hp.com \
--cc=jason.low2@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@us.ibm.com \
--cc=terry.rudd@hpe.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=torvalds@linux-foundation.org \
--cc=waiman.long@hpe.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®