Re: [RFC PATCH-tip v2 1/6] locking/osq: Make lock/unlock proper acquire/release barrier
From: Davidlohr Bueso <dave@stgolabs.net>
Date: 2016-06-17 01:12:13
Also in:
linux-arch, linux-s390, lkml
From: Davidlohr Bueso <dave@stgolabs.net>
Date: 2016-06-17 01:12:13
Also in:
linux-arch, linux-s390, lkml
On Wed, 15 Jun 2016, Peter Zijlstra wrote:
Yeah, see a few patches further in this series, where he guards a variables with the osq_lock.
So one problem I have with all this is that if we are hardening osq_lock/unlock() because of some future use that is specific to rwsems, then we will immediately be hurting mutexes for no good reason. Thanks, Davidlohr