How to Install and Uninstall ibacm Package on openSUSE Leap
Last updated: January 11,2025
1. Install "ibacm" package
In this section, we are going to explain the necessary steps to install ibacm on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
ibacm
Copied
2. Uninstall "ibacm" package
In this section, we are going to explain the necessary steps to uninstall ibacm on openSUSE Leap:
$
sudo zypper remove
ibacm
Copied
3. Information about the ibacm package on openSUSE Leap
Information for package ibacm:
------------------------------
Repository : Main Repository
Name : ibacm
Version : 42.0-150500.1.3
Arch : x86_64
Vendor : SUSE LLC
Installed Size : 189.6 KiB
Installed : No
Status : not installed
Source package : rdma-core-42.0-150500.1.3.src
Upstream URL : https://github.com/linux-rdma/rdma-core
Summary : InfiniBand Communication Manager Assistant
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.
------------------------------
Repository : Main Repository
Name : ibacm
Version : 42.0-150500.1.3
Arch : x86_64
Vendor : SUSE LLC
Installed Size : 189.6 KiB
Installed : No
Status : not installed
Source package : rdma-core-42.0-150500.1.3.src
Upstream URL : https://github.com/linux-rdma/rdma-core
Summary : InfiniBand Communication Manager Assistant
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.