Re: [PATCH] Document Linux's memory barriers [try #4]

Sergei Organov <[email protected]> wrote:

> > +In addition, accesses to "volatile" memory locations and volatile asm
> > +statements act as implicit compiler barriers.
> 
> This last statement seems to contradict with what GCC manual says about
> volatile asm statements:

Perhaps I should say "compiler memory barrier", since it doesn't prevent
instructions from being moved, but rather merely affects the ordering of
memory accesses and volatile instructions.

Hmmm... Is atomic_read() a compiler memory barrier? It isn't a CPU memory
barrier, but it does touch explicitly volatile memory.

David
-
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] Document Linux's memory barriers [try #4]
    • From: Sergei Organov <[email protected]>

• References:
  • Re: [PATCH] Document Linux's memory barriers [try #4]
    • From: Sergei Organov <[email protected]>
  • [PATCH] Document Linux's memory barriers [try #4]
    • From: David Howells <[email protected]>

• Prev by Date: Re: question: pid space semantics.
• Next by Date: Re: 2.6.16-rc6-rt1
• Previous by thread: Re: [PATCH] Document Linux's memory barriers [try #4]
• Next by thread: Re: [PATCH] Document Linux's memory barriers [try #4]
• 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]