Re: [PATCH] Document Linux's memory barriers

This has been needed for quite some time but needs some more
additions:

1) Access to i/o mapped memory does not need memory barriers.

2) Explain difference between mb() and barrier().

3) Explain wmb() versus mmiowb()

Give some more examples of correct usage in drivers.
-
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/

---

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

• Prev by Date: Re: RT patch and arch/i386/kernel/time.c question
• Next by Date: Re: de2104x: interrupts before interrupt handler is registered
• Previous by thread: [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]