Chris Snook <[email protected]> wrote: > cpu_relax() contains a barrier, so it should do the right thing. For non-smp > architectures, I'm concerned about interacting with interrupt handlers. Some > drivers do use atomic_* operations. I'm not sure that actually answers my question. Why not smp_rmb()? David - 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/
- Follow-Ups:
- Re: [PATCH 6/24] make atomic_read() behave consistently on frv
- From: Chris Snook <[email protected]>
- Re: [PATCH 6/24] make atomic_read() behave consistently on frv
- References:
- Re: [PATCH 6/24] make atomic_read() behave consistently on frv
- From: Chris Snook <[email protected]>
- Re: [PATCH 6/24] make atomic_read() behave consistently on frv
- From: Chris Snook <[email protected]>
- [PATCH 6/24] make atomic_read() behave consistently on frv
- From: Chris Snook <[email protected]>
- Re: [PATCH 6/24] make atomic_read() behave consistently on frv
- From: David Howells <[email protected]>
- Re: [PATCH 6/24] make atomic_read() behave consistently on frv
- Prev by Date: Re: [PATCH 00/16] Permit filesystem local caching [try #3]
- Next by Date: Re: 2.6.23-rc2-mm2 build error on MIPS and ARM
- Previous by thread: Re: [PATCH 6/24] make atomic_read() behave consistently on frv
- Next by thread: Re: [PATCH 6/24] make atomic_read() behave consistently on frv
- Index(es):
 |