Hi Konstantin, On 05/26/2014 03:57 PM, Ananyev, Konstantin wrote: > In most cases just a compiler barrier is enough, but there are few exceptions. > Always using fence instructions - means introduce unnecessary slowdown for > cases, when order is guaranteed. > No using fences in cases, when they are needed - means introduce race window > and possible data corruption. > That's why right now people can use either rte_compiler_barrier() or > mb/rmb/wmb - whatever is appropriate for particular case.
OK, so let's drop this patch for now. Thank you for reviewing and commenting. Regards, Olivier
