Re: [PATCH] PPC lll_mutex_unlock_force write barrier

Alexander Terekhov writes:

> Sort of. First off, unless I'm just missing and/or misunderstanding
> something, you've put it in the wrong place. Also, a write barrier 
> isn't enough here. mutex.unlock also needs a read barrier.

Actually I was refering to lll_mutex_unlock_force which stuffs a 0 into 
the lock word then calls lll_futex_wake. This is different from 
lll_mutex_unlock, which uses atomic_exchange_rel,  which includes all the 
required synchronization.