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

David Howells writes:

> > # define smp_read_barrier_depends()     do { } while(0)
> 
> What's this one meant to do?

On most CPUs, if you load one value and use the value you get to
compute the address for a second load, there is an implicit read
barrier between the two loads because of the dependency.  That's not
true on alpha, apparently, because of the way their caches are
structured.  The smp_read_barrier_depends is a read barrier that you
use between two loads when there is already a dependency between the
loads, and it is a no-op on everything except alpha (IIRC).

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] Document Linux's memory barriers [try #2]
  - From: Ivan Kokshaysky <[email protected]>

References:
- Re: [PATCH] Document Linux's memory barriers [try #2]
  - From: Matthew Wilcox <[email protected]>
- [PATCH] Document Linux's memory barriers
  - From: David Howells <[email protected]>
- [PATCH] Document Linux's memory barriers [try #2]
  - From: David Howells <[email protected]>
- Re: [PATCH] Document Linux's memory barriers [try #2]
  - From: Alan Cox <[email protected]>
- Re: [PATCH] Document Linux's memory barriers [try #2]
  - From: David Howells <[email protected]>

Prev by Date: Re: [PATCH] Document Linux's memory barriers [try #2]
Next by Date: Re: [PATCH] Document Linux's memory barriers
Previous by thread: Re: [PATCH] Document Linux's memory barriers [try #2]
Next by thread: Re: [PATCH] Document Linux's memory barriers [try #2]
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]