How to Install and Uninstall ibacm.x86_64 Package on Fedora 34
Last updated: November 14,2024
1. Install "ibacm.x86_64" package
Please follow the guidance below to install ibacm.x86_64 on Fedora 34
$
sudo dnf update
Copied
$
sudo dnf install
ibacm.x86_64
Copied
2. Uninstall "ibacm.x86_64" package
Learn how to uninstall ibacm.x86_64 on Fedora 34:
$
sudo dnf remove
ibacm.x86_64
Copied
$
sudo dnf autoremove
Copied
3. Information about the ibacm.x86_64 package on Fedora 34
Last metadata expiration check: 4:38:11 ago on Tue Sep 6 08:10:37 2022.
Available Packages
Name : ibacm
Version : 37.2
Release : 2.fc34
Architecture : x86_64
Size : 90 k
Source : rdma-core-37.2-2.fc34.src.rpm
Repository : updates
Summary : InfiniBand Communication Manager Assistant
URL : https://github.com/linux-rdma/rdma-core
License : GPLv2 or BSD
Description : The ibacm daemon helps reduce the load of managing path record lookups on
: large InfiniBand fabrics by providing a user space implementation of what
: is functionally similar to an ARP cache. The use of ibacm, when properly
: configured, can reduce the SA packet load of a large IB cluster from O(n^2)
: to O(n). The ibacm daemon is started and normally runs in the background,
: user applications need not know about this daemon as long as their app
: uses librdmacm to handle connection bring up/tear down. The librdmacm
: library knows how to talk directly to the ibacm daemon to retrieve data.
Available Packages
Name : ibacm
Version : 37.2
Release : 2.fc34
Architecture : x86_64
Size : 90 k
Source : rdma-core-37.2-2.fc34.src.rpm
Repository : updates
Summary : InfiniBand Communication Manager Assistant
URL : https://github.com/linux-rdma/rdma-core
License : GPLv2 or BSD
Description : The ibacm daemon helps reduce the load of managing path record lookups on
: large InfiniBand fabrics by providing a user space implementation of what
: is functionally similar to an ARP cache. The use of ibacm, when properly
: configured, can reduce the SA packet load of a large IB cluster from O(n^2)
: to O(n). The ibacm daemon is started and normally runs in the background,
: user applications need not know about this daemon as long as their app
: uses librdmacm to handle connection bring up/tear down. The librdmacm
: library knows how to talk directly to the ibacm daemon to retrieve data.