Thread (12 messages) 12 messages, 3 authors, 2014-01-23

Re: [PATCH v10 1/4] qrwlock: A queue read/write lock implementation

From: Peter Zijlstra <peterz@infradead.org>
Date: 2014-01-23 17:38:56
Also in: lkml

On Thu, Jan 23, 2014 at 09:15:38AM -0800, Linus Torvalds wrote:
On Thu, Jan 23, 2014 at 9:12 AM, Waiman Long [off-list ref] wrote:
quoted
I thought that all atomic RMW instructions are memory barrier.
On x86 they are. Not necessarily elsewhere.
quoted
If they are not, what kind of barrier should be added?
smp_mb__before_atomic_xyz() and smp_mb__after_atomic_xyz() will do it,
and are no-op (well, barriers - I don't think it matters) on x86.
Right, which on PPC are sync, whereas the release need only have lwsync.

And ARM can actually do atomic_sub_release() but cannot do it with an
additional smp_*__after() construct.

Do we care enough to introduce atomic_sub_release() for them?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help