| commit | 602d37f5dee52f628fa141b8edfaa537fda606a9 | [log] [tgz] |
|---|---|---|
| author | Asaf Mazor <amazor@nvidia.com> | Thu Nov 13 10:58:06 2025 +0200 |
| committer | Nicolas Morey <nmorey@suse.com> | Mon Nov 24 15:59:02 2025 +0100 |
| tree | 7ae5e1e801d4f563fa46463ae85dd149277bcd89 | |
| parent | f7175f5900a3991e17a66b7b277320aec7843e77 [diff] |
libibumad: allow choose port with state DOWN in case of explicit user port
[ Upstream commit 862aede44e4f961fa1ea8aa24410097682ef7d56 ]
Today libibumad rejects ports that are not ACTIVE during selection, which
prevents users from targeting a specific port that is administratively DOWN.
This change permits selecting a port in DOWN state when the user has
explicitly specified the port and the device (e.g., by index/identifier).
Automatic port selection behavior is unchanged and will continue to prefer
only ACTIVE ports. Validation of the requested port’s existence and basic
attributes remains intact.
if user explicitly chose device name AND:
- port number
- port is 0 and device is switch
- Only one port for device
we skip the verification of port state.
This is mainly done to suport opensm standalone feature
Fixes: be54b52e94be ("libibumad: Add new API to support SMI/GSI seperation")
Signed-off-by: Asaf Mazor <amazor@nvidia.com>
Signed-off-by: Nicolas Morey <nmorey@suse.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’