On 27 April 2017 at 17:21, Jarno Rajahalme <ja...@ovn.org> wrote: > Specify the event mask with CT commit including bits for CT features > exposed at the OVS interface (mark and label changes in addition to > basic creation and destruction of conntrack entries). > > Without this any listener of conntrack update events will typically > (depending on system configuration) receive events for each L4 (e.g., > TCP) state machine change, which can multiply the number of events > received per connection. > > By including the new, related, and destroy events any listener of new > conntrack events gets notified of new related and non-related > connections, and any listener of destroy events will get notified of > deleted (typically timed out) conntrack entries. > > By including the flags for mark and labels, any listener of conntrack > update events gets notified whenever the connmark or conntrack labels > are changed from the values reported within the new events. > > VMware-BZ: #1837218 > Signed-off-by: Jarno Rajahalme <ja...@ovn.org> > Acked-by: Joe Stringer <j...@ovn.org> > --- > v5: Use addresses in the loopback range and zero port numbers in the probe > to avoid hitting any real conntrack entries.
Thanks for spinning this new version out, it seems unlikely to clash with existing connections now. LGTM. _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
