Configuring hardware offloading

As a cluster administrator, you can configure hardware offloading on compatible nodes to increase data processing performance and reduce load on host CPUs.

About hardware offloading

Open vSwitch hardware offloading is a method of processing network tasks by diverting them away from the CPU and offloading them to a dedicated processor on a network interface controller. As a result, clusters can benefit from faster data transfer speeds, reduced CPU workloads, and lower computing costs.

The key element for this feature is a modern class of network interface controllers known as SmartNICs. A SmartNIC is a network interface controller that is able to handle computationally-heavy network processing tasks. In the same way that a dedicated graphics card can improve graphics performance, a SmartNIC can improve network performance. In each case, a dedicated processor improves performance for a specific type of processing task.

In OKD, you can configure hardware offloading for bare metal nodes that have a compatible SmartNIC. Hardware offloading is configured and enabled by the SR-IOV Network Operator.

Hardware offloading is not compatible with all workloads or application types. Only the following two communication types are supported:

  • pod-to-pod

  • pod-to-service, where the service is a ClusterIP service backed by a regular pod

In all cases, hardware offloading takes place only when those pods and services are assigned to nodes that have a compatible SmartNIC. Suppose, for example, that a pod on a node with hardware offloading tries to communicate with a service on a regular node. On the regular node, all the processing takes place in the kernel, so the overall performance of the pod-to-service communication is limited to the maximum performance of that regular node. Hardware offloading is not compatible with DPDK applications.

Enabling hardware offloading on a node, but not configuring pods to use, it can result in decreased throughput performance for pod traffic. You cannot configure hardware offloading for pods that are managed by OKD.

Supported devices

Hardware offloading is supported on the following network interface controllers:

Table 1. Supported network interface controllers
ManufacturerModelVendor IDDevice ID

Mellanox

MT27800 Family [ConnectX‑5]

15b3

1017

Mellanox

MT28880 Family [ConnectX‑5 Ex]

15b3

1019

Mellanox

MT2892 Family [ConnectX‑6 Dx]

15b3

101d

Mellanox

MT2894 Family [ConnectX-6 Lx]

15b3

101f

Mellanox

MT42822 BlueField-2 in ConnectX-6 NIC mode

15b3

a2d6

Prerequisites

Configuring a machine config pool for hardware offloading

To enable hardware offloading, you must first create a dedicated machine config pool and configure it to work with the SR-IOV Network Operator.

Prerequisites

  • You installed the OpenShift CLI (oc).

  • You have access to the cluster as a user with the cluster-admin role.

Procedure

  1. Create a machine config pool for machines you want to use hardware offloading on.

    1. Create a file, such as mcp-offloading.yaml, with content like the following example:

      1. apiVersion: machineconfiguration.openshift.io/v1
      2. kind: MachineConfigPool
      3. metadata:
      4.   name: mcp-offloading (1)
      5. spec:
      6.   machineConfigSelector:
      7.     matchExpressions:
      8.       - {key: machineconfiguration.openshift.io/role, operator: In, values: [worker,mcp-offloading]} (1)
      9.   nodeSelector:
      10.     matchLabels:
      11.       node-role.kubernetes.io/mcp-offloading: "" (2)
      1The name of your machine config pool for hardware offloading.
      2This node role label is used to add nodes to the machine config pool.

    2. Apply the configuration for the machine config pool:

      1. $ oc create -f mcp-offloading.yaml

  2. Add nodes to the machine config pool. Label each node with the node role label of your pool:

    1. $ oc label node worker-2 node-role.kubernetes.io/mcp-offloading=""

  3. Optional: To verify that the new pool is created, run the following command:

    1. $ oc get nodes

    Example output

    1. NAME       STATUS   ROLES                   AGE   VERSION
    2. master-0   Ready    master                  2d    v1.28.5
    3. master-1   Ready    master                  2d    v1.28.5
    4. master-2   Ready    master                  2d    v1.28.5
    5. worker-0   Ready    worker                  2d    v1.28.5
    6. worker-1   Ready    worker                  2d    v1.28.5
    7. worker-2   Ready    mcp-offloading,worker   47h   v1.28.5
    8. worker-3   Ready    mcp-offloading,worker   47h   v1.28.5

  4. Add this machine config pool to the SriovNetworkPoolConfig custom resource:

    1. Create a file, such as sriov-pool-config.yaml, with content like the following example:

      1. apiVersion: sriovnetwork.openshift.io/v1
      2. kind: SriovNetworkPoolConfig
      3. metadata:
      4.   name: sriovnetworkpoolconfig-offload
      5.   namespace: openshift-sriov-network-operator
      6. spec:
      7.   ovsHardwareOffloadConfig:
      8.     name: mcp-offloading (1)
      1The name of your machine config pool for hardware offloading.

    2. Apply the configuration:

      1. $ oc create -f <SriovNetworkPoolConfig_name>.yaml

      When you apply the configuration specified in a SriovNetworkPoolConfig object, the SR-IOV Operator drains and restarts the nodes in the machine config pool.

      It might take several minutes for a configuration changes to apply.

Configuring the SR-IOV network node policy

You can create an SR-IOV network device configuration for a node by creating an SR-IOV network node policy. To enable hardware offloading, you must define the .spec.eSwitchMode field with the value "switchdev".

The following procedure creates an SR-IOV interface for a network interface controller with hardware offloading.

Prerequisites

  • You installed the OpenShift CLI (oc).

  • You have access to the cluster as a user with the cluster-admin role.

Procedure

  1. Create a file, such as sriov-node-policy.yaml, with content like the following example:

    1. apiVersion: sriovnetwork.openshift.io/v1
    2. kind: SriovNetworkNodePolicy
    3. metadata:
    4.   name: sriov-node-policy (1)
    5.   namespace: openshift-sriov-network-operator
    6. spec:
    7.   deviceType: netdevice (2)
    8.   eSwitchMode: "switchdev" (3)
    9.   nicSelector:
    10.     deviceID: "1019"
    11.     rootDevices:
    12.     - 0000:d8:00.0
    13.     vendor: "15b3"
    14.     pfNames:
    15.     - ens8f0
    16.   nodeSelector:
    17.     feature.node.kubernetes.io/network-sriov.capable: "true"
    18.   numVfs: 6
    19.   priority: 5
    20.   resourceName: mlxnics
    1The name for the custom resource object.
    2Required. Hardware offloading is not supported with vfio-pci.
    3Required.

  2. Apply the configuration for the policy:

    1. $ oc create -f sriov-node-policy.yaml

    When you apply the configuration specified in a SriovNetworkPoolConfig object, the SR-IOV Operator drains and restarts the nodes in the machine config pool.

    It might take several minutes for a configuration change to apply.

An example SR-IOV network node policy for OpenStack

The following example describes an SR-IOV interface for a network interface controller (NIC) with hardware offloading on OpenStack.

An SR-IOV interface for a NIC with hardware offloading on OpenStack

  1. apiVersion: sriovnetwork.openshift.io/v1
  2. kind: SriovNetworkNodePolicy
  3. metadata:
  4.   name: ${name}
  5.   namespace: openshift-sriov-network-operator
  6. spec:
  7.   deviceType: switchdev
  8.   isRdma: true
  9.   nicSelector:
  10.     netFilter: openstack/NetworkID:${net_id}
  11.   nodeSelector:
  12.     feature.node.kubernetes.io/network-sriov.capable: 'true'
  13.   numVfs: 1
  14.   priority: 99
  15.   resourceName: ${name}

Improving network traffic performance using a virtual function

Follow this procedure to assign a virtual function to the OVN-Kubernetes management port and increase its network traffic performance.

This procedure results in the creation of two pools: the first has a virtual function used by OVN-Kubernetes, and the second comprises the remaining virtual functions.

Prerequisites

  • You installed the OpenShift CLI (oc).

  • You have access to the cluster as a user with the cluster-admin role.

Procedure

  1. Add the network.operator.openshift.io/smart-nic label to each worker node with a SmartNIC present by running the following command:

    1. $ oc label node <node-name> network.operator.openshift.io/smart-nic=

    Use the oc get nodes command to get a list of the available nodes.

  2. Create a policy named sriov-node-mgmt-vf-policy.yaml for the management port with content such as the following example:

    1. apiVersion: sriovnetwork.openshift.io/v1
    2. kind: SriovNetworkNodePolicy
    3. metadata:
    4.   name: sriov-node-mgmt-vf-policy
    5.   namespace: openshift-sriov-network-operator
    6. spec:
    7.   deviceType: netdevice
    8.   eSwitchMode: "switchdev"
    9.   nicSelector:
    10.     deviceID: "1019"
    11.     rootDevices:
    12.     - 0000:d8:00.0
    13.     vendor: "15b3"
    14.     pfNames:
    15.     - ens8f0#0-0 (1)
    16.   nodeSelector:
    17.     network.operator.openshift.io/smart-nic: ""
    18.   numVfs: 6 (2)
    19.   priority: 5
    20.   resourceName: mgmtvf
    1Replace this device with the appropriate network device for your use case. The #0-0 part of the pfNames value reserves a single virtual function used by OVN-Kubernetes.
    2The value provided here is an example. Replace this value with one that meets your requirements. For more information, see SR-IOV network node configuration object in the Additional resources section.

  3. Create a policy named sriov-node-policy.yaml with content such as the following example:

    1. apiVersion: sriovnetwork.openshift.io/v1
    2. kind: SriovNetworkNodePolicy
    3. metadata:
    4.   name: sriov-node-policy
    5.   namespace: openshift-sriov-network-operator
    6. spec:
    7.   deviceType: netdevice
    8.   eSwitchMode: "switchdev"
    9.   nicSelector:
    10.     deviceID: "1019"
    11.     rootDevices:
    12.     - 0000:d8:00.0
    13.     vendor: "15b3"
    14.     pfNames:
    15.     - ens8f0#1-5 (1)
    16.   nodeSelector:
    17.     network.operator.openshift.io/smart-nic: ""
    18.   numVfs: 6 (2)
    19.   priority: 5
    20.   resourceName: mlxnics
    1Replace this device with the appropriate network device for your use case.
    2The value provided here is an example. Replace this value with the value specified in the sriov-node-mgmt-vf-policy.yaml file. For more information, see SR-IOV network node configuration object in the Additional resources section.

    The sriov-node-mgmt-vf-policy.yaml file has different values for the pfNames and resourceName keys than the sriov-node-policy.yaml file.

  4. Apply the configuration for both policies:

    1. $ oc create -f sriov-node-policy.yaml
    1. $ oc create -f sriov-node-mgmt-vf-policy.yaml

  5. Create a Cluster Network Operator (CNO) ConfigMap in the cluster for the management configuration:

    1. Create a ConfigMap named hardware-offload-config.yaml with the following contents:

      1. apiVersion: v1
      2. kind: ConfigMap
      3. metadata:
      4.     name: hardware-offload-config
      5.     namespace: openshift-network-operator
      6. data:
      7.     mgmt-port-resource-name: openshift.io/mgmtvf

    2. Apply the configuration for the ConfigMap:

      1. $ oc create -f hardware-offload-config.yaml

Additional resources

Creating a network attachment definition

After you define the machine config pool and the SR-IOV network node policy, you can create a network attachment definition for the network interface card you specified.

Prerequisites

  • You installed the OpenShift CLI (oc).

  • You have access to the cluster as a user with the cluster-admin role.

Procedure

  1. Create a file, such as net-attach-def.yaml, with content like the following example:

    1. apiVersion: "k8s.cni.cncf.io/v1"
    2. kind: NetworkAttachmentDefinition
    3. metadata:
    4.   name: net-attach-def (1)
    5.   namespace: net-attach-def (2)
    6.   annotations:
    7.     k8s.v1.cni.cncf.io/resourceName: openshift.io/mlxnics (3)
    8. spec:
    9.   config: '{"cniVersion":"0.3.1","name":"ovn-kubernetes","type":"ovn-k8s-cni-overlay","ipam":{},"dns":{}}'
    1The name for your network attachment definition.
    2The namespace for your network attachment definition.
    3This is the value of the spec.resourceName field you specified in the SriovNetworkNodePolicy object.

  2. Apply the configuration for the network attachment definition:

    1. $ oc create -f net-attach-def.yaml

Verification

  • Run the following command to see whether the new definition is present:

    1. $ oc get net-attach-def -A

    Example output

    1. NAMESPACE         NAME             AGE
    2. net-attach-def    net-attach-def   43h

Adding the network attachment definition to your pods

After you create the machine config pool, the SriovNetworkPoolConfig and SriovNetworkNodePolicy custom resources, and the network attachment definition, you can apply these configurations to your pods by adding the network attachment definition to your pod specifications.

Procedure

  • In the pod specification, add the .metadata.annotations.k8s.v1.cni.cncf.io/networks field and specify the network attachment definition you created for hardware offloading:

    1. ....
    2. metadata:
    3.   annotations:
    4.     v1.multus-cni.io/default-network: net-attach-def/net-attach-def (1)
    1The value must be the name and namespace of the network attachment definition you created for hardware offloading.