Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures

On Wed, Aug 15, 2007 at 05:23:10PM -0700, Paul E. McKenney wrote:

On Thu, Aug 16, 2007 at 08:12:48AM +0800, Herbert Xu wrote:

quoted

On Wed, Aug 15, 2007 at 04:53:35PM -0700, Paul E. McKenney wrote:

quoted

quoted

quoted

Communicating between process context and interrupt/NMI handlers using
per-CPU variables.

Remeber we're talking about atomic_read/atomic_set.  Please
cite the actual file/function name you have in mind.

Yep, we are indeed talking about atomic_read()/atomic_set().

We have been through this issue already in this thread.

Sorry, but I must've missed it.  Could you cite the file or
function for my benefit?

I might summarize the thread if there is interest, but I am not able to
do so right this minute.

Thanks.  But I don't need a summary of the thread, I'm asking
for an extant code snippet in our kernel that benefits from
the volatile change and is not part of a busy-wait.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} [off-list ref]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt