Re: [PATCH] Document Linux's memory barriers

On Tue, 2006-03-07 at 18:30 +0000, David Howells wrote:

> True, I suppose. I should make it clear that these accessor functions imply
> memory barriers, if indeed they do,

They don't, but according to Documentation/DocBook/deviceiobook.tmpl
they are performed by the compiler in the order specified.

They also convert between PCI byte order and CPU byte order.  If you
want to avoid that, you need the __raw_* versions, which are not
guaranteed to be provided by all arches.

	<b

-
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
    • From: Andi Kleen <[email protected]>

• References:
  • Re: [PATCH] Document Linux's memory barriers
    • From: Andi Kleen <[email protected]>
  • [PATCH] Document Linux's memory barriers
    • From: David Howells <[email protected]>
  • Re: [PATCH] Document Linux's memory barriers
    • From: David Howells <[email protected]>

• Prev by Date: Re: [PATCH] slab: fix offslab_limit in calculate_slab_order (Was: Slab corruption in 2.6.16-rc5-mm2)
• Next by Date: Re: [PATCH] Document Linux's memory barriers
• Previous by thread: Re: [PATCH] Document Linux's memory barriers
• Next by thread: Re: [PATCH] Document Linux's memory barriers
• 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]