FYI HW offload applied to OVS master ;)
//Eelco
-------- Forwarded Message --------
Subject: Re: [ovs-dev] [PATCH V11 00/33] Introducing HW offload support
for openvswitch
Date: Thu, 15 Jun 2017 12:15:20 +0200
From: Simon Horman <[email protected]>
To: Roi Dayan <[email protected]>
CC: [email protected], Shahar Klein <[email protected]>, Hadar Hen
Zion <[email protected]>, Rony Efraim <[email protected]>, Flavio
Leitner <[email protected]>, Jiri Pirko <[email protected]>, Marcelo
Ricardo Leitner <[email protected]>, Or Gerlitz
<[email protected]>, Andy Gospodarek <[email protected]>
On Tue, Jun 13, 2017 at 06:03:22PM +0300, Roi Dayan wrote:
This patch series introduces rule offload functionality to dpif-netlink
via netdev ports new flow offloading API. The user can specify whether to
enable rule offloading or not via OVS configuration. Netdev providers
are able to implement netdev flow offload API in order to offload rules.
This patch series also implements one offload scheme for netdev-linux,
using TC flower classifier, which was chosen because its sort of natural
to state OVS DP rules for this classifier. However, the code can be
extended to support other classifiers such as U32, eBPF, etc which support
offload as well.
The use-case we are currently addressing is the newly sriov switchdev mode
in the Linux kernel which was introduced in version 4.8.
This series was tested against sriov vfs vports representors of the
Mellanox 100G ConnectX-4 series exposed by the mlx5 kernel driver.
The feature is disabled by default and can be enabled by setting
other_config:hw-offload to True.
Currently offloading is done for rules consisting on matching on L2 MAC,
L3 IP (not including IP flags), L4 TCP/UDP (not inclduing TCP flags),
VLAN, VXLAN tunnel.
HW offloading is supported only for drop and for single output action with
Thanks Roi,
I have applied these to the master branch
(in two batches; 1 - 7 yesterday and the rest today).
There were some follow-up requests from Flavio for some of the patches,
please lets not forget those.
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
