[openib-general] uDAPL disconnect events

[Jimmy Hill]

I'm running with the latest OpenIB Gen2 uDAPL code (CMA version) and have
encountered a problem with disconnect events. The basic problem is that both
sides have to call dat_ep_disconnect in order to break down a connection
cleanly. It should be possible for just one side (i.e., client) to call
disconnect and the other side wait for and see the disconnect event. That
does not appear to be working. It does however work that way in the old
reference implementation (as it should). I have code that depends on that
functionality and as a result, can not move it to OpenIB Gen2 uDAPL yet. Is
this a known problem?

Changing the flag to DAT_CLOSE_GRACEFUL_FLAG does not change the behavior.
The attached copy of dtest.c is still using the default flag value.

I have attached a modified version of the "dtest" test program which
demonstrates the problem. The "client" will disconnect and exit cleanly. The
"server" will hang waiting for the disconnect event.

thanks,
jimmy

Jimmy Hill
jimmy.hill at us.ibm.com
sobebike at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/general/attachments/20060103/c219c811/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dtest.c
Type: application/octet-stream
Size: 63439 bytes
Desc: not available
URL: <http://lists.openfabrics.org/pipermail/general/attachments/20060103/c219c811/attachment.obj>