kernel-boot: Remove Wants=network-pre.target from initrd
rdma-load-modules@.service has a Wants=network-pre.target.
While this ensures it is ordered before network initialization even
when no other unit explicitly wants network-pre.target, it causes issues
when executed from the initrd.
During the initrd phase, systemd has no visibility into services on the
root filesystem. Triggering network-pre.target in the initrd marks it as
satisfied before switch-root, causing systemd to bypass rootfs services
ordered Before=network-pre.target (such as firewalls or custom network
scripts) once NetworkManager or Wicked starts on the host.
Work around this issue by moving the Wants= and Before= network-pre.target
directives into a drop-in file that is installed only on the root
filesystem and excluded from the initrd.
In the initrd, there is no direct network-pre dependency, but
Before=sysinit.target ensures modules load before sysinit completes.
Post root switch, the drop-in restores the Wants/Before dependencies,
preserving legacy host behavior. Because udev replays device events
after root switch, the service is re-evaluated with its drop-in,
and dependencies execute as expected.
Fixes: 08f689176497 ("Revise systemd dependencies for all units")
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’