| commit | 5083d3af8f0e67a2d2e4ea425b87bebafc545ef0 | [log] [tgz] |
|---|---|---|
| author | Or Har-Toov <ohartoov@nvidia.com> | Thu Sep 04 16:47:24 2025 +0300 |
| committer | Yishai Hadas <yishaih@nvidia.com> | Wed Jan 07 09:53:17 2026 +0200 |
| tree | 54882039c145d0a25cba6805c5f7e93749275431 | |
| parent | d4870bddee0005792a10476e172bdc85a4d04f9d [diff] |
verbs: Add IBV_EVENT_DEVICE_SPEED_CHANGE to async events Introduce IBV_EVENT_DEVICE_SPEED_CHANGE asynchronous event, which is triggered when one or many of the device's port speeds change due to configuration or state updates. This is especially useful in scenarios such as VF LAG or Multiport LAG configuration, where the effective speed of a VF can change if one of the PFs in the LAG changes state. After receiving this event, applications can use ibv_query_port_speed() on specific ports to check which ones have changed and obtain their new speeds. The event is generated at the device level to avoid flooding the user with many separate notifications when multiple ports are affected simultaneously, such as when a PF with many SFs changes state or when all ports are part of a bonded device that updates speed. Users can then query only those ports they care about for details. Signed-off-by: Or Har-Toov <ohartoov@nvidia.com> Reviewed-by: Patrisious Haddad <phaddad@nvidia.com> Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
This is the userspace components for the Linux Kernel's drivers/infiniband subsystem. Specifically this contains the userspace libraries for the following device nodes:
The userspace component of the libibverbs RDMA kernel drivers are included under the providers/ directory. Support for the following Kernel RDMA drivers is included:
Additional service daemons are provided for:
This project uses a cmake based build system. Quick start:
$ bash build.sh
build/bin will contain the sample programs and build/lib will contain the shared libraries. The build is configured to run all the programs ‘in-place’ and cannot be installed.
$ apt-get install build-essential cmake gcc libudev-dev libnl-3-dev libnl-route-3-dev ninja-build pkg-config valgrind python3-dev cython3 python3-docutils pandoc
Supported releases:
$ dnf builddep redhat/rdma-core.spec
NOTE: Fedora Core uses the name ‘ninja-build’ for the ‘ninja’ command.
$ zypper install cmake gcc libnl3-devel libudev-devel ninja pkg-config valgrind-devel python3-devel python3-Cython python3-docutils pandoc
Install required packages:
$ yum install cmake gcc libnl3-devel libudev-devel make pkgconfig valgrind-devel
Developers on CentOS 7 or Amazon Linux 2 are suggested to install more modern tooling for the best experience.
CentOS 7:
$ yum install epel-release $ yum install cmake3 ninja-build pandoc
Amazon Linux 2:
$ amazon-linux-extras install epel $ yum install cmake3 ninja-build pandoc
NOTE: EPEL uses the name ‘ninja-build’ for the ‘ninja’ command, and ‘cmake3’ for the ‘cmake’ command.
To set up software RDMA on an existing interface with either of the available drivers, use the following commands, substituting <DRIVER> with the name of the driver of your choice (rdma_rxe or siw) and <TYPE> with the type corresponding to the driver (rxe or siw).
# modprobe <DRIVER> # rdma link add <NAME> type <TYPE> netdev <DEVICE>
Please note that you need version of iproute2 recent enough is required for the command above to work.
You can use either ibv_devices or rdma link to verify that the device was successfully added.
Bugs should be reported to the linux-rdma@vger.kernel.org mailing list In your bug report, please include:
Information about your system:
How to reproduce the bug.
If the bug is a crash, the exact output printed out when the crash occurred, including any kernel messages produced.
See Contributing to rdma-core.
Stable versions are released regularly with backported fixes (see Documentation/stable.md) The current minimum version still maintained is ‘v33.X’