Re: [ovs-dev] [PATCH] ofproto-dpif: Use acquire/release barriers with 'tables_version'.

2017-01-19 Thread Jarno Rajahalme
> On Jan 19, 2017, at 4:49 PM, Jarno Rajahalme wrote: > > >> On Jan 13, 2017, at 12:23 PM, Ben Pfaff wrote: >> >> On Thu, Jan 12, 2017 at 10:17:32AM -0800, Jarno Rajahalme wrote: >>> Use memory_order_release when updating the tables version number to >>> make

Re: [ovs-dev] [PATCH] ofproto-dpif: Use acquire/release barriers with 'tables_version'.

2017-01-19 Thread Jarno Rajahalme
> On Jan 13, 2017, at 12:23 PM, Ben Pfaff wrote: > > On Thu, Jan 12, 2017 at 10:17:32AM -0800, Jarno Rajahalme wrote: >> Use memory_order_release when updating the tables version number to >> make sure no memory accesses before the atomic_store (possibly >> relating to setting up

Re: [ovs-dev] [PATCH] ofproto-dpif: Use acquire/release barriers with 'tables_version'.

2017-01-13 Thread Ben Pfaff
On Thu, Jan 12, 2017 at 10:17:32AM -0800, Jarno Rajahalme wrote: > Use memory_order_release when updating the tables version number to > make sure no memory accesses before the atomic_store (possibly > relating to setting up the new version) are reordered to take place > after the atomic_store,

[ovs-dev] [PATCH] ofproto-dpif: Use acquire/release barriers with 'tables_version'.

2017-01-12 Thread Jarno Rajahalme
Use memory_order_release when updating the tables version number to make sure no memory accesses before the atomic_store (possibly relating to setting up the new version) are reordered to take place after the atomic_store, which makes the new version available to other threads. Correspondingly,