Hi Bernard,
In my previous email, I said "yum install librdmacm-utils.x86_64" , that was one of the reason I failed,
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
libibverbs x86_64 13-7.el7 base 194 k
replacing libmthca.x86_64 1.0.6-4.el6
librdmacm-utils x86_64 13-7.el7 base 77 k
rdma-core-devel x86_64 13-7.el7 base 194 k
replacing libibverbs-devel.x86_64 1.1.8-4.el6
replacing librdmacm-devel.x86_64 1.0.21-0.el6
Installing for dependencies:
ibacm x86_64 13-7.el7 base 75 k
libibcm x86_64 13-7.el7 base 14 k
Updating for dependencies:
librdmacm x86_64 13-7.el7 base 59 k
if I confirm to install, many of my lib packages will be automatically replaced by newest virsion that yum provides by default, chaos happens.
and installed all the things I needed using 'rpm -i', and compiled librdmacm-1.0.21.tar.gz by hand, then make & make install.
After that, I used rping command within this dir to test:
[root@localhost examples]# strace -f ./rping -s
it prints:
....
[pid 27337] futex(0x61f1a8, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
[pid 27352] futex(0x61f1a8, FUTEX_WAKE_PRIVATE, 1 <unfinished ...>
[pid 27337] <... futex resumed> ) = -1 EAGAIN (Resource temporarily unavailable)
[pid 27352] <... futex resumed> ) = 0
[pid 27337] futex(0x61f1a8, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
and waiting here, after I typed rping -c as below,
[root@localhost examples]# ./rping -c -a 127.0.0.1 -v
the server terminal printed one more line:
[pid 27337] futex(0x61f1a8, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
[pid 27352] futex(0x61f1a8, FUTEX_WAKE_PRIVATE, 1 <unfinished ...>
[pid 27337] <... futex resumed> ) = -1 EAGAIN (Resource temporarily unavailable)
[pid 27352] <... futex resumed> ) = 0
[pid 27337] futex(0x61f1a8, FUTEX_WAIT_PRIVATE, 0, NULL <unfinished ...>
[pid 27352] write(3, "\f\0\0\0\10\0H\0010]\235\241\312\177\0\0", 16
and stuck here, empty after the number '16', nothing new happened afterwards, if ctrl+c the client and rping -c again, the client termital would print:
[root@localhost examples]# ./rping -c -a 127.0.0.1 -v
cma event RDMA_CM_EVENT_UNREACHABLE, error -110
the server side prints:(secont attempt without using ftrace -f)
server DISCONNECT EVENT...
wait for RDMA_READ_ADV state 10
-----------------------------------
I have set /etc/security/limits.conf
and [root@localhost examples]# lsmod |grep rdma
xprtrdma 50626 0
rdma_ucm 22316 2
ib_uverbs 42495 10 ib_ucm,rdma_ucm
rdma_cm 43138 4 xprtrdma,ib_iser,rdma_ucm,ib_isert
ib_addr 14070 1 rdma_cm
ib_cm 42717 5 rdma_cm,ib_srp,ib_ucm,ib_srpt,ib_ipoib
ib_sa 29615 5 rdma_cm,ib_cm,ib_srp,rdma_ucm,ib_ipoib
iw_cm 18669 1 rdma_cm
ib_core 82647 17 siw,rdma_cm,ib_cm,ib_sa,iw_cm,xprtrdma,ib_mad,ib_srp,ib_ucm,ib_iser,ib_srpt,ib_umad,ib_uverbs,rdma_ucm,ib_ipoib,ib_isert,ib_mthca
sunrpc 271941 8 nfsd,auth_rpcgss,lockd,xprtrdma,nfs_acl
[root@localhost home]# ibv_devices
seems nothing about configuration goes wrong, however, my colleague did the similar operations as me, could successfully rping under ubuntu 16.04 with kernel 3.10.107.
btw. I make sure that firewalld and selinux have all been disabled.
thanks.
黄勋
Xun Huang
烽火通信科技股份有限公司(Fiberhome Telecommunication Technologies Co.,LTD)