You've already forked linux-apfs
mirror of
https://github.com/linux-apfs/linux-apfs.git
synced 2026-05-01 15:00:59 -07:00
IA64: Slim down __clear_bit_unlock
__clear_bit_unlock does not need to perform atomic operations on the variable. Avoid a cmpxchg and simply do a store with release semantics. Add a barrier to be safe that the compiler does not do funky things. Tony: Use intrinsic rather than inline assembler Signed-off-by: Christoph Lameter <clameter@sgi.com> Acked-by: Nick Piggin <nickpiggin@yahoo.com.au> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Tony Luck <tony.luck@intel.com>
This commit is contained in:
committed by
Tony Luck
parent
c63a119036
commit
a3ebdb6c42
@@ -124,10 +124,21 @@ clear_bit_unlock (int nr, volatile void *addr)
|
||||
/**
|
||||
* __clear_bit_unlock - Non-atomically clear a bit with release
|
||||
*
|
||||
* This is like clear_bit_unlock, but the implementation may use a non-atomic
|
||||
* store (this one uses an atomic, however).
|
||||
* This is like clear_bit_unlock, but the implementation uses a store
|
||||
* with release semantics. See also __raw_spin_unlock().
|
||||
*/
|
||||
#define __clear_bit_unlock clear_bit_unlock
|
||||
static __inline__ void
|
||||
__clear_bit_unlock(int nr, volatile void *addr)
|
||||
{
|
||||
__u32 mask, new;
|
||||
volatile __u32 *m;
|
||||
|
||||
m = (volatile __u32 *)addr + (nr >> 5);
|
||||
mask = ~(1 << (nr & 31));
|
||||
new = *m & mask;
|
||||
barrier();
|
||||
ia64_st4_rel_nta(m, new);
|
||||
}
|
||||
|
||||
/**
|
||||
* __clear_bit - Clears a bit in memory (non-atomic version)
|
||||
|
||||
Reference in New Issue
Block a user