nova/releasenotes/notes/sriov-ovs-offload-1c3fe79e847f8c8f.yaml
Moshe Levi ccc1def0f5 hardware offload support for openvswitch
In Kernel 4.8 we introduced Traffic Control (TC see [1]) hardware offloads
framework for SR-IOV VFs which allows us to configure the NIC [2].
Subsequent OVS patches [3] allows us to use the TC framework
to offload OVS datapath rules. This feature is supported in OVS 2.8.0.

This patch adds support for VIF_TYPE_OVS with vnic_type direct

blueprint sriov-ovs-offload

[1] http://netdevconf.org/1.2/papers/efraim-gerlitz-sriov-ovs-final.pdf
[2] https://patchwork.ozlabs.org/patch/738176/
[3] https://mail.openvswitch.org/pipermail/ovs-dev/2017-April/330606.html

Change-Id: I3f38954bc5cf7b1690182dc8af45078eea275aa4
2017-08-03 13:30:30 +00:00

14 lines
688 B
YAML

---
features:
- |
Adds support to OVS vif type with direct port (SR-IOV).
In order to use this OVS acceleration mode, ``openvswitch`` 2.8.0
and 'Linux Kernel' 4.8 are required. This feature allows control of
an SR-IOV virtual function (VF) via OpenFlow control plane and gain
improved performance of 'Open vSwitch'. Please note that in Pike
release we can't differentiate between SR-IOV hardware and OVS offloaded
on the same host. This limitation should be resolved when the
enable-sriov-nic-features will be completed.
Until then operators can use host aggregates to ensure that they can
schedule instances on specific hosts based on hardware.