Re: atomics: document that linux expects certain atomic behaviour from unsigned long

> Pretty much everywhere that uses RCU for example does so using atomic pointer
> loads and stores. The nastiest issue IMO actually is reloading the value
> through the pointer even if it isn't explicitly dereferenced. RCU gets this
> right with ACCESS_ONCE. Probably a lot of code using basic types does not.
> x86 atomic_read maybe should be using ACCESS_ONCE too...

I'm pretty sure it should. gcc makes no guarantees about not being clever
with accesses.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html