Quoting r. Sean Hefty <[EMAIL PROTECTED]>: > Subject: Re: [PATCH ] RFC IB/cm do not track remote QPN in timewait state > > >Here's an idea: > >how about we move the whole timewait thing to low level driver, > >starting timer automatically upon QP destroy? > > I've thought about this too, and I think this may end up making the most > sense. > How would the driver determine how long the QP should remain in timewait,
Need to look into this - likely we can just add a call for that. Roland? > and > how would you sync that with the CM's timewait? There's no need for CM or any other entity to track timewait QP in this setup - we can remove TIMEWAIT_EXIT event or pass it up immediately. The role of timewait as I see it is to prevent reuse of the QP number too soon. If verbs do that, CM does not need to. > (Userspace QPs are often > connected using TCP, rather than through the IB CM.) These actually want timewait too, they just don't know it :) -- MST _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
