[openib-general] [PATCHv2][RFC] kDAPL: use cm timers insteadof own

[Sean Hefty]

>> From a CM perspective, this sounds fine.  Note that the CM timeout will
>not
>> occur until the number of retries has been met.  So I don't know if the
>> timeout passed to dapl_ep_connect() should convert directly into the
>> remote_cm_response_timeout, or needs to be divided by the number of
>retries.
>
>So, are you saying that if you have a timeout of 4 seconds (you pass in
>20) and you have retries set to 2, that it will fail after 8 seconds?
>
>James, what is the timeout value passed into dapl_ep_connect mean, the
>total timeout time?  Or how much for each retry?

If you pass in a timeout of 4 seconds with retries to 2, the call will
timeout in 12 seconds.  The request will be sent 3 times (2 retries).  I
should also note that the CM timeout includes the packet lifetime (round
trip time) in its timeout calculation, but this should be small.

- Sean