The trunk is [almost] right. It has nice error handling, and a bunch of other features.
However, part of this bug report is troubling. We might want to check why it doesn't exhaust all possible addressed before giving up on an endpoint. George. PS: I'm not saying that we should back-port this in the 1.8 ... On Wed, Aug 13, 2014 at 3:33 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com > wrote: > On Aug 13, 2014, at 12:52 PM, George Bosilca <bosi...@icl.utk.edu> wrote: > > > There are many differences between the trunk and 1.8 regarding the TCP > BTL. The major I remember about is that the TCP in the trunk is reporting > errors to the upper level via the callbacks attached to fragments, while > the 1.8 TCP BTL doesn't. > > > > So, I guess that once a connection to a particular endpoint fails, the > trunk is getting the errors reported via the cb and then takes some drastic > measure. In the 1.8 we might fallback and try another IP address before > giving up. > > Does that has any effect on performance? > > I.e., should we bring this change to v1.8? > > Or, put simply: which way is Right? > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2014/08/15638.php >
