Index of /freebsd/head/contrib/ofed/librdmacm
Name Last modified Size Description
Parent Directory 29-Oct-2014 04:29 -
AUTHORS 27-Sep-2011 02:14 1k
COPYING 27-Sep-2011 02:14 19k
ChangeLog 27-Sep-2011 02:14 0k
INSTALL 27-Sep-2011 02:14 0k
Makefile.am 27-Sep-2011 02:14 2k
Makefile.in 27-Sep-2011 02:14 39k
NEWS 27-Sep-2011 02:14 0k
aclocal.m4 27-Sep-2011 02:14 256k
config.h.in 27-Sep-2011 02:14 2k
config/ 27-Sep-2011 02:14 -
configure 27-Sep-2011 02:14 708k
configure.in 27-Sep-2011 02:14 2k
examples/ 29-Oct-2014 04:29 -
include/ 27-Sep-2011 02:14 -
librdmacm.spec 27-Sep-2011 02:14 2k
librdmacm.spec.in 27-Sep-2011 02:14 2k
man/ 27-Sep-2011 02:14 -
src/ 27-Sep-2011 02:14 -
This README is for userspace RDMA cm library.
Building
========
To make this directory, run:
./autogen.sh && ./configure && make && make install
Typically the autogen and configure steps only need be done the first
time unless configure.in or Makefile.am changes.
Libraries are installed by default at /usr/local/lib.
Device files
============
The userspace CMA uses a single device file regardless of the number
of adapters or ports present.
To create the appropriate character device file automatically with
udev, a rule like
KERNEL="rdma_cm", NAME="infiniband/%k", MODE="0666"
can be used. This will create the device node named
/dev/infiniband/rdma_cm
or you can create it manually
mknod /dev/infiniband/rdma_cm c 231 255
Common issues
=============
Using multiple interfaces
The librdmacm does support multiple interfaces. To make use
of multiple interfaces, however, you need to instruct linux
to only send ARP reples on the interface targetted in the ARP
request. This can be done using a command similar to the
following:
sysctl -w net.ipv4.conf.all.arp_ignore=2
Without this change, it's possible for linux to resopnd to ARP
requests on a different interface (IP address) than the IP
address carried in the ARP request. This causes the RDMA stack
to incorrectly map the remote IP address to the wrong RDMA
device.