Port Type Management/VPI Cards Configuration
Ports of ConnectX-4 adapter cards and above can be individually configured to work as InfiniBand or Ethernet ports. By default, both VPI ports are initialized as InfiniBand ports. If you wish to change the port type, use the mlxconfig script after the driver is loaded.
For further information on how to set the port type, please refer to the MFT User Manual (nvidia.com/en-us/networking/ → Products → Software → InfiniBand/VPI Software → MFT—Firmware Tools)
Counters are used to provide information about how well an operating system, an application, a service, or a driver is performing. The counter data help determine system bottlenecks and fine-tune the system and application performance. The operating system, network, and devices provide counter data that an application can consume to provide users with a graphical view of how well the system is performing.
The counter index is a Queue Pair (QP) attribute given in the QP context. Multiple QPs may be associated with the same counter set. If multiple QPs share the same counter, the counter value will represent the cumulative total.
- RoCE counters are available only through sysfs located under:
- # /sys/class/infiniband/<device>/ports/*/counters/
- # /sys/class/infiniband/<device>/ports/*/hw_counters/
For mlx5 port and RoCE counters, refer to the Understanding mlx5 Linux Counters Community post.
Physical Function can also read Virtual Functions' port counters through sysfs located under # /sys/class/net/<interface_name>/device/sriov/<index>/stats/
The ethtool counters are counted in different places, according to which they are divided into groups. Each counters group may also have different counter types.
For the full list of supported ethtool counters, refer to the Understanding mlx5 ethtool Counters community post.
To avoid network interface renaming after boot or driver restart, create a file names "/etc/udev/rules.d/85-net-persistent-names.rules" with rules to set explicit interface names (the number, 85, must be more than 83).
Example for Ethernet interfaces:
Example for IPoIB interfaces:
Interrupt Request (IRQ) Naming
Once IRQs are allocated by the driver, they are named
mlx5_comp<x>@pci:<pci_addr>. The IRQs corresponding to the channels in use are renamed to
<interface>-<x>, while the rest maintain their default name.
The mlx5_core driver allocates all IRQs during loading time to support the maximum possible number of channels. Once the driver is up, no further IRQs are freed or allocated. Changing the number of working channels does not re-allocate or free the IRQs.
The following example demonstrates how reducing the number of channels affects the IRQs names.