[ovs-dev] [PATCH V11 00/33] Introducing HW offload support for openvswitch

Joe Stringer joe at ovn.org
Thu Jun 15 23:36:25 UTC 2017


On 15 June 2017 at 03:15, Simon Horman <simon.horman at netronome.com> wrote:
> 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.

Thanks all who've been involved in this work, it's a good start and I
look forward to seeing it become more fleshed out and become more
useful for a wider range of use cases.

Looking over the commits, I see that there was no mention of
experimental status yet so I'll send a followup patch shortly to
address this. I don't think that this should surprise anyone, as I
raised this a few times with people at netdev 2.1.


More information about the dev mailing list