>I understand that, however, currently the code I am working with (iser)
>wait to get both flushes on all the posted work requests AND disconnect
>or address-change event to mark the couple as
>disconnected, clear it up and signal higher level to reconnect. I'll
>have to look what is the way to go
Sean Hefty wrote:
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.
okay, thanks for explaining this.
You should be able to destroy the rdma_cm_id at anytime
>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_ti
Hi Sean,
I'm trying to understand what is the time out (e.g for DREQ) used by
the ib cm when called by the rdmacm through rdma_connect.
1st, going empirically it looks like 100 seconds pass between a call
to rdma_disconnect and getting RDMA_CM_EVENT_DISCONNECTED after taking
the relevant IB port
