I wouldn't put too much fate in my memory either. What I recall is that the multi-link code was written mainly for the PS4, where the supervisor would limit the bandwidth per socket to about 60% of the hardware capabilities. Thus, by using multiple links (in fact sockets between a set of peers) we could aggregate the bandwidth.
I do not recall all the details, but I think the code was supposed to increase the latency and decrease the bandwidth for the case where multiple TCP modules were using the same interface. It would certainly be interesting to re-write this code, it is 10 years old. George. On Wed, Apr 26, 2017 at 3:24 PM, Barrett, Brian via devel < devel@lists.open-mpi.org> wrote: > George - > > Do you remember why you adjusted both the latency and bandwidth for > secondary links when using multi-link support with the TCP BTL [1]? I > think I understand why, but your memory of 10 years ago is hopefully more > accurate than my reverse engineering ;). > > Thanks, > > Brian > > > > [1] https://github.com/open-mpi/ompi/blame/master/opal/mca/ > btl/tcp/btl_tcp_component.c#L497 > _______________________________________________ > devel mailing list > devel@lists.open-mpi.org > https://rfd.newmexicoconsortium.org/mailman/listinfo/devel >
_______________________________________________ devel mailing list devel@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
