kernel-boot: Add naming support for sub-function (SF) RDMA devices
PCI Sub-function (SF) is anchored on the auxiliary bus rather than
directly on the PCI bus, so by_pci() previously rejected them as
"Non-PCI" and they fell back to their kernel-assigned name.
Detect this case by treating an "auxiliary" device subsystem as a valid
parent: read the stable 'sfnum' attribute from the aux device and
follow its 'device' symlink up to the underlying PCI BDF. The PCI
parent can be a PF or an SR-IOV VF; feeding the BDF into the
existing get_virtfn_info() / fill_pci_info() path handles both layouts
uniformly. The PCI-derived portion of the name is composed unchanged;
an S<sfnum> suffix is then appended last, after any f<func>/v<vf>
components, since SF identity is independent of them.
Examples:
SF on a multi-function PF:
parent 0000:c1:00.0, sfnum 88 -> rocep193s0f0S88
SF on an SR-IOV VF (VF-SF):
parent 0000:c1:00.4, sfnum 99 -> rocep193s0f0v0S99
Also update Documentation/udev.md and the rdma-persistent-naming.rules
header comment with the new S<sfnum> suffix.
Signed-off-by: Jiri Pirko <jiri@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’