From: Peter Zijlstra <peterz@infradead.org>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: Waiman Long <waiman.long@hpe.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
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>,
Terry Rudd <terry.rudd@hpe.com>,
"Paul E. McKenney" <paulmck@us.ibm.com>,
Jason Low <jason.low2@hp.com>
Subject: Re: [RFC][PATCH 1/3] locking/mutex: Rework mutex::owner
Date: Tue, 23 Aug 2016 23:03:54 +0200 [thread overview]
Message-ID: <20160823210354.GY10153@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1471985566.2916.18.camel@linux.intel.com>
On Tue, Aug 23, 2016 at 01:52:46PM -0700, Tim Chen wrote:
> On Tue, 2016-08-23 at 15:55 -0400, Waiman Long wrote:
> > On 08/23/2016 08:46 AM, Peter Zijlstra wrote:
> >
> > I have 2 more comments about the code.
> > 1) There are a couple of places where you only use 0x3 in mutex.c. They
> > should be replaced by the symbolic name instead.
>
> May be easier to read if (owner & 0x3) and
> (owner & ~0x3) are changed to something like
> _owner_flag(owner) and _owner_task(owner).
Yes that would work. Something like the below..
Note the ';' in the last "-" line that currently ensures we always take
the slow path.
----
--- a/kernel/locking/mutex.c
+++ b/kernel/locking/mutex.c
@@ -55,7 +55,17 @@ EXPORT_SYMBOL(__mutex_init);
#define MUTEX_FLAG_WAITERS 0x01
#define MUTEX_FLAG_HANDOFF 0x02
-#define MUTEX_FLAG_ALL 0x03
+#define MUTEX_FLAGS 0x03
+
+static inline struct task_struct *__owner_task(unsigned long owner)
+{
+ return (struct task_struct *)(owner & ~MUTEX_FLAGS);
+}
+
+static inline unsigned long __owner_flags(unsigned long owner)
+{
+ return owner & MUTEX_FLAGS;
+}
/*
* Atomically try to take the lock when it is available
@@ -65,7 +75,7 @@ static inline bool __mutex_trylock(struc
unsigned long owner, new_owner;
owner = atomic_long_read(&lock->owner);
- if (owner & ~0x03)
+ if (__owner_task(owner))
return false;
new_owner = owner | (unsigned long)current;
@@ -466,14 +476,14 @@ void __sched mutex_unlock(struct mutex *
if (owner & MUTEX_FLAG_HANDOFF)
break;
- old = atomic_long_cmpxchg_release(&lock->owner, owner, owner & 0x03);
+ old = atomic_long_cmpxchg_release(&lock->owner, owner, __owner_flags(owner));
if (old == owner)
break;
owner = old;
}
- if (owner & 0x03);
+ if (__owner_flags(owner))
__mutex_unlock_slowpath(lock, owner);
}
EXPORT_SYMBOL(mutex_unlock);
next prev parent reply other threads:[~2016-08-23 21:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 12:46 [RFC][PATCH 0/3] locking/mutex: Rewrite basic mutex Peter Zijlstra
2016-08-23 12:46 ` [RFC][PATCH 1/3] locking/mutex: Rework mutex::owner Peter Zijlstra
2016-08-23 19:55 ` Waiman Long
2016-08-23 20:52 ` Tim Chen
2016-08-23 21:03 ` Peter Zijlstra [this message]
2016-08-23 21:09 ` Peter Zijlstra
2016-08-23 20:17 ` Waiman Long
2016-08-23 20:31 ` Peter Zijlstra
2016-08-24 9:56 ` Will Deacon
2016-08-24 15:34 ` Peter Zijlstra
2016-08-24 16:52 ` Peter Zijlstra
2016-08-24 16:54 ` Will Deacon
2016-08-23 12:46 ` [RFC][PATCH 2/3] locking/mutex: Allow MUTEX_SPIN_ON_OWNER when DEBUG_MUTEXES Peter Zijlstra
2016-08-23 12:46 ` [RFC][PATCH 3/3] locking/mutex: Add lock handoff to avoid starvation Peter Zijlstra
2016-08-23 12:56 ` Peter Zijlstra
[not found] ` <57BCA869.1050501@hpe.com>
2016-08-23 20:32 ` Peter Zijlstra
2016-08-24 19:50 ` Waiman Long
2016-08-25 8:11 ` Peter Zijlstra
2016-08-23 16:17 ` [RFC][PATCH 0/3] locking/mutex: Rewrite basic mutex Davidlohr Bueso
2016-08-23 16:35 ` Jason Low
2016-08-23 16:57 ` Peter Zijlstra
2016-08-23 19:36 ` Waiman Long
2016-08-23 20:41 ` Peter Zijlstra
2016-08-23 22:34 ` Waiman Long
2016-08-24 1:13 ` Jason Low
2016-08-25 12:32 ` Peter Zijlstra
2016-08-25 15:43 ` Peter Zijlstra
2016-08-25 16:33 ` Waiman Long
2016-08-25 16:35 ` Peter Zijlstra
2016-08-27 18:27 ` Ingo Molnar
2016-08-25 19:11 ` huang ying
2016-08-25 19:26 ` Peter Zijlstra
2016-08-23 18:53 ` Linus Torvalds
2016-08-23 20:34 ` 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=20160823210354.GY10153@twins.programming.kicks-ass.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.