Skip to content

Commit 11e37a7

Browse files
kquinn1204kquinn1204
committed
adding note about vfio-pci
1 parent 3d6e8c6 commit 11e37a7

File tree

2 files changed

+22
-14
lines changed

2 files changed

+22
-14
lines changed

‎modules/nw-sriov-interface-level-sysctl-basic-node-policy.adoc

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,9 @@
44

55
:_content-type: PROCEDURE
66
[id="nw-basic-example-setting-one-sysctl-flag-node-policy_{context}"]
7-
= Setting one sysctl flag on nodes with SR-IOV network devices
7+
= Setting one sysctl flag on nodes with SR-IOV network devices
88

9-
The SR-IOV Network Operator adds the `SriovNetworkNodePolicy.sriovnetwork.openshift.io` custom resource definition (CRD) to {product-title}. You can configure an SR-IOV network device by creating a `SriovNetworkNodePolicy` custom resource (CR).
9+
The SR-IOV Network Operator adds the `SriovNetworkNodePolicy.sriovnetwork.openshift.io` custom resource definition (CRD) to {product-title}. You can configure an SR-IOV network device by creating a `SriovNetworkNodePolicy` custom resource (CR).
1010

1111
[NOTE]
1212
====
@@ -15,11 +15,11 @@ When applying the configuration specified in a `SriovNetworkNodePolicy` object,
1515
It can take several minutes for a configuration change to apply.
1616
====
1717

18-
Follow this procedure to create a `SriovNetworkNodePolicy` custom resource (CR).
18+
Follow this procedure to create a `SriovNetworkNodePolicy` custom resource (CR).
1919

2020
.Procedure
2121

22-
. Create an `SriovNetworkNodePolicy` custom resource (CR). For example, save the following YAML as the file `policyoneflag-sriov-node-network.yaml`:
22+
. Create an `SriovNetworkNodePolicy` custom resource (CR). For example, save the following YAML as the file `policyoneflag-sriov-node-network.yaml`:
2323
+
2424
[source,yaml]
2525
----
@@ -49,13 +49,17 @@ spec:
4949
<7> The NIC selector identifies the device for the Operator to configure. You do not have to specify values for all the parameters. It is recommended to identify the network device with enough precision to avoid selecting a device unintentionally.
5050
If you specify `rootDevices`, you must also specify a value for `vendor`, `deviceID`, or `pfNames`. If you specify both `pfNames` and `rootDevices` at the same time, ensure that they refer to the same device. If you specify a value for `netFilter`, then you do not need to specify any other parameter because a network ID is unique.
5151
<8> Optional: An array of one or more physical function (PF) names for the device.
52-
<9> Optional: The driver type for the virtual functions. The only allowed values are `netdevice` and `vfio-pci`. The default value is `netdevice`.
53-
For a Mellanox NIC to work in DPDK mode on bare metal nodes, use the `netdevice` driver type and set `isRdma` to `true`.
52+
<9> Optional: The driver type for the virtual functions. The only allowed value is `netdevice`.
53+
For a Mellanox NIC to work in DPDK mode on bare metal nodes, set `isRdma` to `true`.
5454
<10> Optional: Configures whether to enable remote direct memory access (RDMA) mode. The default value is `false`.
5555
If the `isRdma` parameter is set to `true`, you can continue to use the RDMA-enabled VF as a normal network device. A device can be used in either mode.
5656
Set `isRdma` to `true` and additionally set `needVhostNet` to `true` to configure a Mellanox NIC for use with Fast Datapath DPDK applications.
5757
+
58-
58+
[NOTE]
59+
====
60+
The `vfio-pci` driver type is not supported.
61+
====
62+
+
5963
. Create the `SriovNetworkNodePolicy` object:
6064
+
6165
[source,terminal]
@@ -72,7 +76,7 @@ After applying the configuration update, all the pods in `sriov-network-operator
7276
$ oc get sriovnetworknodestates -n openshift-sriov-network-operator <node_name> -o jsonpath='{.status.syncStatus}'
7377
----
7478
+
75-
.Example output
79+
.Example output
7680
[source,terminal]
7781
----
7882
Succeeded

‎modules/nw-sriov-interface-level-sysctl-bonded-node-policy.adoc

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,9 @@
44

55
:_content-type: CONCEPT
66
[id="nw-setting-all-sysctls-flag-node-policy-bonded_{context}"]
7-
= Setting all sysctl flag on nodes with bonded SR-IOV network devices
7+
= Setting all sysctl flag on nodes with bonded SR-IOV network devices
88

9-
The SR-IOV Network Operator adds the `SriovNetworkNodePolicy.sriovnetwork.openshift.io` custom resource definition (CRD) to {product-title}. You can configure an SR-IOV network device by creating a `SriovNetworkNodePolicy` custom resource (CR).
9+
The SR-IOV Network Operator adds the `SriovNetworkNodePolicy.sriovnetwork.openshift.io` custom resource definition (CRD) to {product-title}. You can configure an SR-IOV network device by creating a `SriovNetworkNodePolicy` custom resource (CR).
1010

1111
[NOTE]
1212
====
@@ -15,7 +15,7 @@ When applying the configuration specified in a SriovNetworkNodePolicy object, th
1515
It might take several minutes for a configuration change to apply.
1616
====
1717

18-
Follow this procedure to create a `SriovNetworkNodePolicy` custom resource (CR).
18+
Follow this procedure to create a `SriovNetworkNodePolicy` custom resource (CR).
1919

2020
.Procedure
2121

@@ -49,13 +49,17 @@ spec:
4949
<7> The NIC selector identifies the device for the Operator to configure. You do not have to specify values for all the parameters. It is recommended to identify the network device with enough precision to avoid selecting a device unintentionally.
5050
If you specify `rootDevices`, you must also specify a value for `vendor`, `deviceID`, or `pfNames`. If you specify both `pfNames` and `rootDevices` at the same time, ensure that they refer to the same device. If you specify a value for `netFilter`, then you do not need to specify any other parameter because a network ID is unique.
5151
<8> Optional: An array of one or more physical function (PF) names for the device.
52-
<9> Optional: The driver type for the virtual functions. The only allowed values are `netdevice` and `vfio-pci`. The default value is `netdevice`.
53-
For a Mellanox NIC to work in DPDK mode on bare metal nodes, use the `netdevice` driver type and set `isRdma` to `true`.
52+
<9> Optional: The driver type for the virtual functions. The only allowed value is `netdevice`.
53+
For a Mellanox NIC to work in DPDK mode on bare metal nodes, set `isRdma` to `true`.
5454
<10> Optional: Configures whether to enable remote direct memory access (RDMA) mode. The default value is `false`.
5555
If the `isRdma` parameter is set to `true`, you can continue to use the RDMA-enabled VF as a normal network device. A device can be used in either mode.
5656
Set `isRdma` to `true` and additionally set `needVhostNet` to `true` to configure a Mellanox NIC for use with Fast Datapath DPDK applications.
5757
+
58-
58+
[NOTE]
59+
====
60+
The `vfio-pci` driver type is not supported.
61+
====
62+
+
5963
. Create the SriovNetworkNodePolicy object:
6064
+
6165
[source,terminal]

0 commit comments

Comments
 (0)