On Thu, Feb 27, 2014 at 02:13:08PM -0800, Joe Stringer wrote: > This patch makes it the caller's responsibility to initialize a > per-thread 'state' object and pass it down to the dpif_flow_dump_next() > implementation. The implementation can expect to be called from multiple > threads with the same 'iter' and different 'state' objects. > > When flow_dump_next() returns non-zero, the implementation must ensure > that subsequent calls with the same arguments also return non-zero. > Subsequent calls with the same 'iter' and different 'state' may return > zero, but should make progress towards returning non-zero. > > Signed-off-by: Joe Stringer <joestrin...@nicira.com>
Missing & in the atomic_destroy() call here (I'll fix it): > + atomic_read(&iter->status, &dump_status); > + atomic_destroy(iter->status); _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
