Skip to content

Commit bb7fd8a

Browse files
authored
clarifies the non usage of SRIOV Bonding with DPDK (#849)
1 parent 706818c commit bb7fd8a

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

asciidoc/product/atip-features.adoc

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -560,6 +560,11 @@ spec:
560560
===== Bond CNI with SR-IOV
561561
Using the Bond CNI with SR-IOV is fairly straight forward. For more details on how to set up SR-IOV, see <<sriov>>. As described there, you have to create `SriovNetworkNodePolicies` that defines `resourceNames`, as well as number of virtual functions and such. The `resourceNames` are being used by the `SriovNetwork` which is used as interfaces in the pod definition. The bond definition is exactly the same as for the MACVLAN and host device cases.
562562

563+
[NOTE]
564+
====
565+
Bond CNI with SR-IOV is only applicable to SRIOV Virtual Functions (VF) using the kernel driver. Userspace driver VFs - such as those used in DPDK workloads - can not be bonded with the Bond CNI.
566+
====
567+
563568
[#sriov]
564569
=== SR-IOV
565570

0 commit comments

Comments
 (0)