diff options
author | Tim Chen <tim.c.chen@linux.intel.com> | 2014-01-22 00:36:00 +0100 |
---|---|---|
committer | Ingo Molnar <mingo@kernel.org> | 2014-01-28 13:13:27 +0100 |
commit | e72246748ff006ab928bc774e276e6ef5542f9c5 (patch) | |
tree | b3021f1615d2088ce20fc02bd61e9f2baab72dd1 /REPORTING-BUGS | |
parent | locking/mutexes/mcs: Correct barrier usage (diff) | |
download | linux-e72246748ff006ab928bc774e276e6ef5542f9c5.tar.xz linux-e72246748ff006ab928bc774e276e6ef5542f9c5.zip |
locking/mutexes/mcs: Restructure the MCS lock defines and locking code into its own file
We will need the MCS lock code for doing optimistic spinning for rwsem
and queued rwlock. Extracting the MCS code from mutex.c and put into
its own file allow us to reuse this code easily.
We also inline mcs_spin_lock and mcs_spin_unlock functions
for better efficiency.
Note that using the smp_load_acquire/smp_store_release pair used in
mcs_lock and mcs_unlock is not sufficient to form a full memory barrier
across cpus for many architectures (except x86). For applications that
absolutely need a full barrier across multiple cpus with mcs_unlock and
mcs_lock pair, smp_mb__after_unlock_lock() should be used after mcs_lock.
Reviewed-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Signed-off-by: Tim Chen <tim.c.chen@linux.intel.com>
Signed-off-by: Davidlohr Bueso <davidlohr@hp.com>
Signed-off-by: Peter Zijlstra <peterz@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Link: http://lkml.kernel.org/r/1390347360.3138.63.camel@schen9-DESK
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'REPORTING-BUGS')
0 files changed, 0 insertions, 0 deletions