On Tue, 28 Jun 2005, Jesse Barnes wrote:
> On ia64 at least, the unlock is only a one way barrier. The store to
> realease the lock uses release semantics (since the lock is declared
> volatile), which implies that prior stores are visible before the
> unlock occurs, but subsequent accesses can 'float up' above the unlock.
> See http://www.gelato.unsw.edu.au/linux-ia64/0304/5122.html for some
> more details.
The manual talks about "accesses" not stores. So this applies to loads and
stores. Subsequent accesses can float up but only accesses prior to the
instruction with release semantics (like an unlock) are guaranteed to be
visible.
-
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/
[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]
