Ilya reported a problem with zone limits in particular when a default is set but a zone specific limit is not. As per subject, the series (path 5/5) addresses this issue by creating an entry in the zone limit map as soon as the first packet for a zone is seen (and the default limit is in place). A test was extended to exercise the behavior and make sure the kernel and userspace datapath behave consistently.
Paolo Valerio (5): conntrack: Correctly annotate conntrack member. conntrack: Add zone limit coverage counter. conntrack: Do not use atomics to report zones info. conntrack: Turn zl local limit into atomic. conntrack: Use a per zone default limit. lib/conntrack-private.h | 18 ++- lib/conntrack.c | 241 +++++++++++++++++++++++++++++++--------- lib/conntrack.h | 9 +- lib/dpif-netdev.c | 6 +- tests/system-traffic.at | 64 ++++++++--- 5 files changed, 256 insertions(+), 82 deletions(-) -- 2.45.2 _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
