>2nd, looking on the code, I see that cma_connect_ib uses >CMA_CM_RESPONSE_TIMEOUT >(20) for req.remote_cm_response_timeout and CMA_MAX_CM_RETRIES (15) for >req.max_cm_retries. Looking into the cm code, I see that ib_send_cm_req >sets >cm_id_priv->timeout_ms as a function of the path packet_life_time && >the remote_cm_response_timeout ... with the latter value being 20 and >the >former being 18 (this is a guess) does 100 seconds of a timeout makes >sense to you?
I believe that the IB timeout of 20 is about 4 seconds. If the packet lifetime is 1 second, then each try will take 6 seconds to timeout. For 15 retries, this is close to 100 seconds. You should be able to destroy the rdma_cm_id at anytime. Also, the call to ib_send_cm_drep is called to handle the case where both sides try disconnecting at the same time. The call should be harmless, since the IB CM handles the state checks. - Sean -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
