Removing support for legacy tunnel vport types, as they are not used
with the kernel datapath for about 9 years now.  The last in-tree user
for them in dpif-netlink was Windows datapath that was also removed
recently.

This increases the minimal kernel requirement for tunnel support to
Linux 4.3 that added support for COLLECT_METADATA to various tunnel
devices.  However, this is not a huge loss, as the same kernel version
is required for basic conntrack support, which is a very common action
in most use cases.  Many other features require higher kernel versions
as well.

It will still be possible to use OVS, through without tunnels, on
older kernels.  Users of OOT openvswitch module will still be able to
use tunnels if the main kernel supports them, or if they bring the
tunnel support to the kernel as separate OOT modules implementing
RTM_NEWLINK for desired tunnel types.

The last patch is the main removal, the first 3 are cleanup patches
for the bits left after the kernel module removal form the OVS tree.

Ilya Maximets (4):
  dpif-netlink-rtnl: More consistent handling of the unsupported SRv6.
  utilities: ovs-dev: Remove modinst command.
  docs: ipsec: Remove references to the out-of-tree kernel module.
  dpif-netlink: Drop support for legacy tunnel vport types.

 Documentation/faq/releases.rst            |  18 ++-
 Documentation/tutorials/ipsec.rst         |   8 +-
 NEWS                                      |   6 +
 lib/dpif-netlink-rtnl.c                   | 117 +----------------
 lib/dpif-netlink-rtnl.h                   |  18 +--
 lib/dpif-netlink.c                        | 148 ++++++----------------
 lib/dpif-netlink.h                        |   5 +-
 tests/system-kmod-macros.at               |   7 -
 tests/system-offloads-testsuite-macros.at |   4 -
 utilities/docker/ovs-override.conf        |   2 -
 utilities/docker/start-ovs                |   1 -
 utilities/ovs-dev.py                      |  35 +----
 12 files changed, 73 insertions(+), 296 deletions(-)

-- 
2.54.0

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

Reply via email to