On 04/25/14 18:56, Hefty, Sean wrote: > Btw, up til now most of the requests regarding CM timeouts has been to > increase it. We need to make sure that we don't end up breaking that. > Even if we set this timeout to 0, the total timeout for a connection > request is 2 x packet lifetime x # retries. With a 1 second packet > lifetime, that's still 30 seconds. What timeout range are you looking > for? The app could always set a separate timer and cancel the request > as well.
What I had noticed is that with the current timeout settings after a cable pull it can take really long before a cm_id object reaches TimeWait exit state. Timeout settings that are between 1/4th and 1/8th of the current settings result in more reasonable behavior. Bart. -- 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
