[EMAIL PROTECTED] wrote on Thu, 03 Jul 2008 13:03 -0700:
> >That makes sense. I couldn't find anyway to get that bit
> >IWCM_F_CONNECT_WAIT cleared (without massive layering violations).
> >Is there anything like rdma_give_up_on_the_connect() that works
> >on the client side? Am I expected just to wait for the transport
> >layer to time out the connect? I could imagine a Ctrl-C situation
> >where immediate client-side cancellation is desired.
>
> From the perspective of the rdma_cm interface, rdma_destroy_id() is
> intended to provide this functionality.
That is a sensible approach. The implementation in iwcm.c just
passively waits for a connection to time out before allowing
rdma_destroy_id() to complete. Maybe I should look at adding a case
in cma_cancel_operation() for CMA_CONNECT that calls into a
device-specific function that can actively quit the connection.
Or should this be a special case in iwcm's destroy_cm_id()? Where
a CONN_SENT state will bypass the check on IWCM_F_CONNECT_WAIT, and
call into a device function that tries to cancel the connection
attepmt first?
-- Pete
_______________________________________________
general mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
