Skip to content

Commit f74a4eb

Browse files
authored
Merge pull request #35276 from jboxman/OSDOCS-2395
OSDOCS-2395: Graduate DPDK to GA
2 parents 3e0dfeb + f059075 commit f74a4eb

File tree

4 files changed

+32
-10
lines changed

4 files changed

+32
-10
lines changed

modules/nw-sriov-dpdk-example-intel.adoc

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -66,17 +66,20 @@ metadata:
6666
namespace: openshift-sriov-network-operator
6767
spec:
6868
networkNamespace: <target_namespace>
69-
ipam: "{}" <1>
69+
ipam: |-
70+
# ... <1>
7071
vlan: <vlan>
7172
resourceName: intelnics
7273
----
73-
<1> Specify an empty object `"{}"` for the ipam CNI plug-in. DPDK works in userspace mode and does not require an IP address.
74+
<1> Specify a configuration object for the ipam CNI plug-in as a YAML block scalar. The plug-in manages IP address assignment for the attachment definition.
7475
+
7576
[NOTE]
7677
=====
7778
See the `Configuring SR-IOV additional network` section for a detailed explanation on each option in `SriovNetwork`.
7879
=====
7980
+
81+
An optional library, app-netutil, provides several API methods for gathering network information about a container's parent pod.
82+
8083
. Create the `SriovNetwork` object by running the following command:
8184
+
8285
[source,terminal]

modules/nw-sriov-dpdk-example-mellanox.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ metadata:
7070
spec:
7171
networkNamespace: <target_namespace>
7272
ipam: |- <1>
73-
...
73+
# ...
7474
vlan: <vlan>
7575
resourceName: mlxnics
7676
----
@@ -80,6 +80,8 @@ spec:
8080
=====
8181
See the `Configuring SR-IOV additional network` section for detailed explanation on each option in `SriovNetwork`.
8282
=====
83+
+
84+
An optional library, app-netutil, provides several API methods for gathering network information about a container's parent pod.
8385

8486
. Create the `SriovNetworkNodePolicy` object by running the following command:
8587
+

modules/nw-sriov-rdma-example-mellanox.adoc

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,8 @@
44

55
[id="example-vf-use-in-rdma-mode-mellanox_{context}"]
66
= Using a virtual function in RDMA mode with a Mellanox NIC
7-
7+
// Extract content for TP notice
8+
// tag::content[]
89
RDMA over Converged Ethernet (RoCE) is the only supported mode when using RDMA
910
on {product-title}.
1011

@@ -73,7 +74,7 @@ metadata:
7374
spec:
7475
networkNamespace: <target_namespace>
7576
ipam: |- <1>
76-
...
77+
# ...
7778
vlan: <vlan>
7879
resourceName: mlxnics
7980
----
@@ -83,6 +84,8 @@ spec:
8384
=====
8485
See the `Configuring SR-IOV additional network` section for detailed explanation on each option in `SriovNetwork`.
8586
=====
87+
+
88+
An optional library, app-netutil, provides several API methods for gathering network information about a container's parent pod.
8689

8790
. Create the `SriovNetworkNodePolicy` object by running the following command:
8891
+
@@ -140,3 +143,4 @@ spec:
140143
----
141144
$ oc create -f mlx-rdma-pod.yaml
142145
----
146+
// end::content[]
Lines changed: 18 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,32 @@
11
[id="using-dpdk-and-rdma"]
2-
= Using virtual functions (VFs) with DPDK and RDMA modes
2+
= Using DPDK and RDMA
33
include::modules/common-attributes.adoc[]
44
:context: using-dpdk-and-rdma
55

66
toc::[]
77

8-
You can use Single Root I/O Virtualization (SR-IOV) network hardware with the Data Plane Development Kit (DPDK) and with remote direct memory access (RDMA).
98

10-
:FeatureName: The Data Plane Development Kit (DPDK)
11-
include::modules/technology-preview.adoc[leveloffset=+0]
9+
The containerized Data Plane Development Kit (DPDK) application is supported on {product-title}. You can use Single Root I/O Virtualization (SR-IOV) network hardware with the Data Plane Development Kit (DPDK) and with remote direct memory access (RDMA).
10+
11+
For information on supported devices, refer to xref:../../networking/hardware_networks/about-sriov.adoc#supported-devices_about-sriov[Supported devices].
1212

1313
include::modules/nw-sriov-dpdk-example-intel.adoc[leveloffset=+1]
1414

1515
include::modules/nw-sriov-dpdk-example-mellanox.adoc[leveloffset=+1]
1616

17-
include::modules/nw-sriov-rdma-example-mellanox.adoc[leveloffset=+1]
17+
[id="example-vf-use-in-rdma-mode-mellanox_{context}"]
18+
== Using a virtual function in RDMA mode with a Mellanox NIC
19+
20+
:FeatureName: RDMA over Converged Ethernet (RoCE)
21+
include::modules/technology-preview.adoc[leveloffset=+0]
22+
23+
// Use a tag to skip header and include content only
24+
include::modules/nw-sriov-rdma-example-mellanox.adoc[tag=content]
25+
26+
[id="{context}_additional_resources"]
27+
== Additional resources
28+
29+
* xref:../../networking/hardware_networks/configuring-sriov-net-attach.adoc#configuring-sriov-net-attach[Configuring an SR-IOV Ethernet network attachment].
30+
* The xref:../../networking/hardware_networks/about-sriov.adoc#nw-sriov-app-netutil_about-sriov[app-netutil library], provides several API methods for gathering network information about a container's parent pod.
1831

1932
:!FeatureName:

0 commit comments

Comments
 (0)