Messages in this thread | | | Date | Thu, 16 Aug 2007 07:41:46 +0800 | From | Herbert Xu <> | Subject | Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures |
| |
On Wed, Aug 15, 2007 at 11:45:20AM -0700, Paul E. McKenney wrote: > On Wed, Aug 15, 2007 at 07:19:57PM +0100, David Howells wrote: > > Herbert Xu <herbert@gondor.apana.org.au> wrote: > > > > > Let's turn this around. Can you give a single example where > > > the volatile semantics is needed in a legitimate way? > > > > Accessing H/W registers? But apart from that... > > 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.
Thanks, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt - 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/
| |