Chris Snook wrote:
This is not a problem, since indirect references will cause the CPU to
fetch the data from memory/cache anyway.
Isn't Zan's sample code (that shows the problem) already using indirect
references?
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- why are some atomic_t's not volatile, while most are?
- From: "Robert P. J. Day" <rpjday@mindspring.com>
- Re: why are some atomic_t's not volatile, while most are?
- From: Jerry Jiang <wjiang@resilience.com>
- Re: why are some atomic_t's not volatile, while most are?
- From: Chris Snook <csnook@redhat.com>
- Re: why are some atomic_t's not volatile, while most are?
- From: "Chris Friesen" <cfriesen@nortel.com>
- Re: why are some atomic_t's not volatile, while most are?
- From: Chris Snook <csnook@redhat.com>
- Re: why are some atomic_t's not volatile, while most are?
- From: "Chris Friesen" <cfriesen@nortel.com>
- Re: why are some atomic_t's not volatile, while most are?
- From: Chris Snook <csnook@redhat.com>
- Re: why are some atomic_t's not volatile, while most are?
- From: "Chris Friesen" <cfriesen@nortel.com>
- Re: why are some atomic_t's not volatile, while most are?
- From: Zan Lynx <zlynx@acm.org>
- Re: why are some atomic_t's not volatile, while most are?
- From: Chris Snook <csnook@redhat.com>
[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]