On Thu, Jul 31, 2014 at 03:21:51PM -0700, Jarno Rajahalme wrote: > Use 'volatile' to enforce a new memory access on each lockless atomic > store and read. Without this a loop consisting of an atomic_read with > memory_order_relaxed would be simply optimized away. Also, using > volatile is cheaper than adding a full compiler barrier (also) in that > case. > > This use of a volatile cast mirrors the Linux kernel ACCESS_ONCE macro. > > Without this change the more rigorous atomic test cases introduced in > a following patch will hang due to the atomic accesses being optimized > away. > > Signed-off-by: Jarno Rajahalme <jrajaha...@nicira.com>
Acked-by: Ben Pfaff <b...@nicira.com> _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
