Has to do with the socket going into the time wait state, which is because it is waiting for any possibly still in flight packets as Caitlin said. From what I was told, there is not really any option to get around this with the Ammasso card. This was back when they were still in business though, and for their ccil driver. Probably better off to use different ports.
-Dennis On Tue, 2006-09-26 at 17:53 -0400, Sundeep Narravula wrote: > > TCP restricts prompt re-use of the same Source/Destination > > Address/Port pair while old traffic could still be in-flight. > > This is generally not an issue because prompt re-use of the > > exact four tuple is rare. > > > > Is there a special reason why your application needs to > > reuse the same port from the active side? If the port number > > is being used to identify the rank, could private data be > > used instead? > > Our application is primarily an invocation of multiple independent parallel > jobs which all need to connect or each other on each invocation. Since > this is a TCP limitation, is there any interface similar to setsockopt > with TCP_NODELAY. We probably need to use different ports otherwise. > > Thanks, > --Sundeep. > > > > > > > > > > _______________________________________________ > openib-general mailing list > [email protected] > http://openib.org/mailman/listinfo/openib-general > > To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general > _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
