Closed kim-tae-kyung closed 3 months ago
Hi @kim-tae-kyung. Thanks for your PR.
I'm waiting for a k8snetworkplumbingwg member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
@kim-tae-kyung thanks for the PR.
@ykulazhenkov any chance you would be interested in reviewing this? Sadly, I'm not all that familiar with the SR-IOV portion of the project, and I don't feel confident reviewing this.
@ykulazhenkov Thanks for your review! I have reflected your comments. You made me realize that there were missing features and duplicated codes.
@phoracek The PR looks good to me. Can you trigger the CI check?
/test pull-e2e-ovs-cni
Thanks a lot for the review @ykulazhenkov
@SchSeba do you also want to take a look before we merge this?
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: kim-tae-kyung, SchSeba, ykulazhenkov
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/lgtm
Thanks to All!
Add support for SR-IOV Virtual Functions (VFs) using both hardware offload (switchdev) and userspace device drivers such as vfio-pci. If the MAC address is provided via arguments, update the VF’s MAC address accordingly using netlink.
What this PR does / why we need it:
This feature is essential for scenarios where SR-IOV VFs require both userspace device drivers and hardware offload. For instance, containerized network functions with Intel E810 may enable eswitch switchdev mode for hardware offload while using the vfio-pci driver for running DPDK or VPP. Another use case is the KubeVirt SR-IOV Interface. After merging this PR, users can create a KubeVirt VM supported by OVS hardware offload without modifying the KubeVirt source code.
Special notes for your reviewer:
Even in scenarios where userspace device drivers are employed, and there is no netdevice for the VF on the host, the CNI should still return the name and sandbox for the VF interface to be recognized by Multus.
Release note: