Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-1441

[RFE] Support changing the eswitch mode

XMLWordPrintable

    • NetworkManager-1.46.0-1.el9
    • 1
    • rhel-sst-network-management
    • ssg_networking
    • 26
    • 2
    • False
    • Hide

      None

      Show
      None
    • Yes
    • NMT - Last NMT changes
    • Hide

      User story
      As a NM user, I want to select the eswitch mode between legacy SRIOV and switchdev.

      Acceptance criteria

      Given a NIC that supports devlink and switchdev mode

      When a NM profile contains the sriov.eswitch-mode property "legacy" or "switchdev"
      Then NM changes the eswitch mode to the requested value just before creating the VFs

      When NM has to change the eswitch mode and the current number of VFs is not 0
      Then change the number of VFs to 0 to avoid errors when setting the eswitch mode, then continue as normal

      Definition of Done

      • The implementation meets the acceptance criteria
      • Unit tests and integration tests if applicable (decided during refinement) are written and passed
      • DocText/DocType is set.
      • The code is part of a downstream build attached to an errata
      Show
      User story As a NM user, I want to select the eswitch mode between legacy SRIOV and switchdev. Acceptance criteria Given a NIC that supports devlink and switchdev mode When a NM profile contains the sriov.eswitch-mode property "legacy" or "switchdev" Then NM changes the eswitch mode to the requested value just before creating the VFs When NM has to change the eswitch mode and the current number of VFs is not 0 Then change the number of VFs to 0 to avoid errors when setting the eswitch mode, then continue as normal Definition of Done The implementation meets the acceptance criteria Unit tests and integration tests if applicable (decided during refinement) are written and passed DocText/DocType is set. The code is part of a downstream build attached to an errata
    • Pass
    • None
    • Enhancement
    • Hide
      .NetworkManager now supports configuring the `switchdev` mode for advanced hardware offload

      With this enhancement, you can configure the following new properties in NetworkManager connection profiles:

      * `sriov.eswitch-mode`
      * `sriov.eswitch-inline-mode`
      * `sriov.eswitch-encap-mode`

      With these properties, you can configure the eSwitch of smart network interface controllers (Smart NICs). For example, use the `sriov.eswitch-mode` setting to change the mode from `legacy SR-IOV` to `switchdev` to use advanced hardware offload features.
      Show
      .NetworkManager now supports configuring the `switchdev` mode for advanced hardware offload With this enhancement, you can configure the following new properties in NetworkManager connection profiles: * `sriov.eswitch-mode` * `sriov.eswitch-inline-mode` * `sriov.eswitch-encap-mode` With these properties, you can configure the eSwitch of smart network interface controllers (Smart NICs). For example, use the `sriov.eswitch-mode` setting to change the mode from `legacy SR-IOV` to `switchdev` to use advanced hardware offload features.
    • Done
    • None

      Description of problem:

      OpenStack team is expecting NetworkManager provide support of
      OVS SR-IOV TC Hardware Offload describe in

      https://docs.openstack.org/neutron/queens/admin/config-ovs-offload.html

      Version-Release number of selected component (if applicable):

      How reproducible:

      Steps to Reproduce:
      1.
      2.
      3.

      Actual results:

      Expected results:

      Additional info:

      User story
      As an OpenStack administrator using RHEL 9.4+, I want NetworkManager to provide support for OpenvSwitch (OVS) SR-IOV Traffic Control (TC) Hardware Offload configuration, so that I can leverage hardware offload capabilities for increased network performance.

      Acceptance criteria
      Given a OpenStack system based on RHEL 9.4+,
      When user apply nmstate YML containing OpenvSwitch TC hardware offloading config,
      Then nmstate will instruct NetworkManager to setup the OVS TC hardware offload describe in https://docs.openstack.org/neutron/queens/admin/config-ovs-offload.html

      Definition of Done

      • The implementation meets the acceptance criteria
      • Unit tests and integration tests if applicable (decided during refinement) are written and passed
      • DocText/DocType is set.
      • The code is part of a downstream build attached to an errata

              ihuguet@redhat.com Inigo Huguet
              fge@redhat.com Gris Ge
              Inigo Huguet Inigo Huguet
              Vladimir Benes Vladimir Benes
              Marc Muehlfeld Marc Muehlfeld
              Votes:
              0 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: