Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures

On Mon, Sep 10, 2007 at 11:59:29AM -0700, Christoph Lameter wrote:
> On Fri, 17 Aug 2007, Segher Boessenkool wrote:
> 
> > "volatile" has nothing to do with reordering.  atomic_dec() writes
> > to memory, so it _does_ have "volatile semantics", implicitly, as
> > long as the compiler cannot optimise the atomic variable away
> > completely -- any store counts as a side effect.
> 
> Stores can be reordered. Only x86 has (mostly) implicit write ordering. So 
> no atomic_dec has no volatile semantics and may be reordered on a variety 
> of processors. Writes to memory may not follow code order on several 
> processors.

The one exception to this being the case where process-level code is
communicating to an interrupt handler running on that same CPU -- on
all CPUs that I am aware of, a given CPU always sees its own writes
in order.

							Thanx, Paul
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
    • From: Christoph Lameter <[email protected]>

• References:
  • Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
    • From: Satyam Sharma <[email protected]>
  • Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
    • From: Paul Mackerras <[email protected]>
  • Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
    • From: Herbert Xu <[email protected]>
  • Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
    • From: Paul Mackerras <[email protected]>
  • Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
    • From: Herbert Xu <[email protected]>
  • Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
    • From: "Ilpo Järvinen" <[email protected]>
  • Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
    • From: Chris Snook <[email protected]>
  • Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
    • From: Christoph Lameter <[email protected]>
  • Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
    • From: Segher Boessenkool <[email protected]>
  • Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
    • From: Christoph Lameter <[email protected]>

• Prev by Date: RE: Health monitor of a multi-threaded process
• Next by Date: Re: [NFS] [BUG] 2.6.23-rc5 kernel BUG at fs/nfs/nfs4xdr.c:945
• Previous by thread: Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
• Next by thread: Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]