lkml.org 
[lkml]   [2007]   [Aug]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: why are some atomic_t's not volatile, while most are?
On Wed, 08 Aug 2007 02:47:53 -0400
Chris Snook <csnook@redhat.com> wrote:

> Chris Friesen wrote:
> > 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?
>
> Yeah, I misinterpreted his conclusion. I thought about this for a
> while, and realized that it's perfectly legal for the compiler to re-use
> a value obtained from atomic_read. All that matters is that the read
> itself was atomic. The use (or non-use) of the volatile keyword is

Sorry, I can't understand it a bit .., Could you do in detail?

-- Jerry


> really more relevant to the other atomic operations. If you want to
> guarantee a re-read from memory, use barrier(). This, incidentally,
> uses volatile under the hood.
>
> -- 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/

\
 
 \ /
  Last update: 2007-08-08 10:25    [W:0.104 / U:0.132 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site