• J
    locking/mutexes: Unlock the mutex without the wait_lock · 1d8fe7dc
    Jason Low 提交于
    When running workloads that have high contention in mutexes on an 8 socket
    machine, mutex spinners would often spin for a long time with no lock owner.
    
    The main reason why this is occuring is in __mutex_unlock_common_slowpath(),
    if __mutex_slowpath_needs_to_unlock(), then the owner needs to acquire the
    mutex->wait_lock before releasing the mutex (setting lock->count to 1). When
    the wait_lock is contended, this delays the mutex from being released.
    We should be able to release the mutex without holding the wait_lock.
    Signed-off-by: NJason Low <jason.low2@hp.com>
    Cc: chegu_vinod@hp.com
    Cc: paulmck@linux.vnet.ibm.com
    Cc: Waiman.Long@hp.com
    Cc: torvalds@linux-foundation.org
    Cc: tglx@linutronix.de
    Cc: riel@redhat.com
    Cc: akpm@linux-foundation.org
    Cc: davidlohr@hp.com
    Cc: hpa@zytor.com
    Cc: andi@firstfloor.org
    Cc: aswin@hp.com
    Cc: scott.norton@hp.com
    Signed-off-by: NPeter Zijlstra <peterz@infradead.org>
    Link: http://lkml.kernel.org/r/1390936396-3962-4-git-send-email-jason.low2@hp.comSigned-off-by: NIngo Molnar <mingo@kernel.org>
    1d8fe7dc
mutex.c 23.5 KB