RE: Synchronizing Bit operations V2
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: "'Christoph Lameter'" <clameter@xxxxxxx>
- Subject: RE: Synchronizing Bit operations V2
- From: "Chen, Kenneth W" <kenneth.w.chen@xxxxxxxxx>
- Date: Thu, 30 Mar 2006 19:14:51 -0800
- Cc: "Nick Piggin" <nickpiggin@xxxxxxxxxxxx>, "Zoltan Menyhart" <Zoltan.Menyhart@xxxxxxxx>, "Boehm, Hans" <hans.boehm@xxxxxx>, "Grundler, Grant G" <grant.grundler@xxxxxx>, <akpm@xxxxxxxx>, <linux-kernel@xxxxxxxxxxxxxxx>, <linux-ia64@xxxxxxxxxxxxxxx>
- In-reply-to: <Pine.LNX.4.64.0603301909590.3145@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Thread-index: AcZUcOq3zmzy2yEaTL6XZJMfzv7kWwAAC0GA
Christoph Lameter wrote on Thursday, March 30, 2006 7:12 PM
> > The use of
> > smp_mb__before_clear_bit();
> > clear_bit( ... );
> >
> > is: all memory operations before this call will be visible before
> > the clear_bit(). To me, that's release semantics.
>
> What of it? Release semantics are not a full fence or memory barrier.
The API did not require a full fence. It is defined as a one way fence.
-
: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Kernel]
[Sparc Linux]
[DCCP]
[Linux ARM]
[Yosemite News]
[Linux SCSI]
[Linux x86_64]
[Linux for Ham Radio]