[ewg] RE: [ofa-general] how do I use uDAPL with iWARP?
Davis, Arlin R
arlin.r.davis at intel.com
Thu Apr 3 10:00:09 PDT 2008
>Client side:
>
>[releng at svbu-qa2950-2 ~]$ DAPL_MAX_INLINE=64 dtest -h 192.168.0.198
>13926 Running as client - OpenIB-cma
>13926 Server Name: 192.168.0.198
>13926 Server Net Address: 192.168.0.198
>13926 Waiting for connect response
>13926 Error unexpected conn event : DAT_CONNECTION_EVENT_UNREACHABLE
>13926 Error connect_ep: DAT_ABORT
>
>Server side:
>
>[releng at svbu-qa2950-1 ~]$ DAPL_MAX_INLINE=64 dtest
>11461 Running as server - OpenIB-cma
>11461 Server waiting for connect request..
>11461 Waiting for connect response
>
>11461 CONNECTED!
>
>11461 Send RMR to remote: snd_msg:
>r_key_ctx=bff,pad=0,va=146db580,len=0x40
>11461 Waiting for remote to send RMR data
>11461 Error waiting on h_dto_rcv_evd: DAT_TIMEOUT_EXPIRED
>11461 Error connect_ep: DAT_TIMEOUT_EXPIRED
>
Interesting that the server gets connected but client doesn't. If you
build the dapl package with --enable-debug and set DAPL_DBG_TYPE=0xffff
we can see what is going on with rdma_cm events on the client side.
See
http://www.openfabrics.org//downloads/dapl/documentation/uDAPL_ofed_test
ing_bkm.pdf for debugging details.
uDAPL uses rdma_cm to connect similar to rping and ib_rdma_lat -c so it
would be helpful to see if you have any luck with either rping or
ib_rdma_lat -c?
BTW: the default OFED 1.3 setting for DAPL_MAX_ININE is 64 so you
shouldn't have to adjust down from OFED 1.2.5 default of 128 anymore for
the chelsio device.
-arlin
More information about the general
mailing list