> Also, whoever wrote "/Documentation/volatiles_are_evil" must not have
The Linux way to handle this is to use gcc memory barriers.
mb()/barrier()/wmb()/rmb()/smp_rmb()/smp_wmb() etc.
Normally everything that volatile can do can be expressed by them.
On x86 such a memory barrier tells gcc that memory might
have been clobbered and needs to be flushed and also prevents the compiler
from reordering memory accesses. On other architectures it also forces ordering
on the CPU level, although that's not needed on x86 (except
in some special situations like using write-combining)
See Documentation/memory-barriers.txt
-Andi
--
