[PATCH 3/5] locking/rtmutex: Use acquire/release semantics

2015-09-30 Thread Davidlohr Bueso
As of 654672d4ba1 (locking/atomics: Add _{acquire|release|relaxed}() variants of some atomic operations) and 6d79ef2d30e (locking, asm-generic: Add _{relaxed|acquire|release}() variants for 'atomic_long_t'), weakly ordered archs can benefit from more relaxed use of barriers when locking and unlocki

Re: [PATCH 3/5] locking/rtmutex: Use acquire/release semantics

2015-09-22 Thread Davidlohr Bueso
On Tue, 22 Sep 2015, Thomas Gleixner wrote: @@ -121,11 +130,14 @@ static inline bool unlock_rt_mutex_safe(struct rt_mutex *lock) * lock(wait_lock); * acquire(lock); */ - return rt_mutex_cm

Re: [PATCH 3/5] locking/rtmutex: Use acquire/release semantics

2015-09-22 Thread Thomas Gleixner
On Mon, 21 Sep 2015, Davidlohr Bueso wrote: > As such, weakly ordered archs can benefit from more relaxed use > of barriers when locking/unlocking. > > Signed-off-by: Davidlohr Bueso > --- > kernel/locking/rtmutex.c | 30 +- > 1 file changed, 21 insertions(+), 9 delet

[PATCH 3/5] locking/rtmutex: Use acquire/release semantics

2015-09-21 Thread Davidlohr Bueso
As such, weakly ordered archs can benefit from more relaxed use of barriers when locking/unlocking. Signed-off-by: Davidlohr Bueso --- kernel/locking/rtmutex.c | 30 +- 1 file changed, 21 insertions(+), 9 deletions(-) diff --git a/kernel/locking/rtmutex.c b/kernel/lo