The series exposes CT limit via DB, adding
user friendly ovs-vsctl interface. The DB value
has priority before the dpctl interface, this is
achieved by storing which CT limit is protected.
The dpctl will return an error if the limit is
already set in DB for that zone.

Ales Musil (3):
  ovs-vsctl: Add limit to CT zone
  vswitchd, ofproto-dpif: Propagate the CT limit from database
  netlink, netdev: Enforce CT limit protection

 NEWS                       |   2 +
 lib/conntrack.c            |  51 +++++++++++-------
 lib/conntrack.h            |   5 +-
 lib/ct-dpif.c              |   9 ++--
 lib/ct-dpif.h              |   5 +-
 lib/dpctl.c                |   4 +-
 lib/dpif-netdev.c          |  12 +++--
 lib/dpif-netlink.c         |  37 +++++++++++--
 lib/dpif-provider.h        |  13 +++--
 ofproto/ofproto-dpif.c     |  41 ++++++++++++++
 ofproto/ofproto-dpif.h     |   5 ++
 ofproto/ofproto-provider.h |   5 ++
 ofproto/ofproto.c          |  16 +++++-
 ofproto/ofproto.h          |   2 +
 tests/ovs-vsctl.at         |  58 ++++++++++++++++++++
 tests/system-traffic.at    |  74 ++++++++++++++++++++++++-
 utilities/ovs-vsctl.8.in   |  20 ++++++-
 utilities/ovs-vsctl.c      | 108 ++++++++++++++++++++++++++++++++++++-
 vswitchd/bridge.c          |   9 ++++
 vswitchd/vswitch.ovsschema |   9 +++-
 vswitchd/vswitch.xml       |   5 ++
 21 files changed, 441 insertions(+), 49 deletions(-)

-- 
2.41.0

_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to