[openib-general] [PATCH ] RFC IB/cm do not track remote QPN in timewait state

[Sean Hefty]

Sean Hefty wrote:
> How would the driver determine how long the QP should remain in timewait

The spec isn't totally clear to me on this, but here's what I can gather:

timewait = packet lifetime x 2 + remote ack delay
local_ack_timeout (in CM REQ) = packet lifetime x 2 + local ack delay

Verbs gets local_ack_timeout through qp_attr.timeout when modifying the QP to 
RTS.  But from 12.7.34, I believe that the local_ack_timeout used by verbs is 
for the remote QP, meaning that:

local_ack_timeout (verbs) = packet lifetime x 2 + remote ack delay

which is also the timewait value.  Do you concur?  If so, then verbs already has 
the timewait value.

- Sean