> If MPI or other middle layer is to implement the multirail, why bother
> even with OFI: implement directly on the device and no need for extra
> OFI overhead.

Well, if MPI wants to write to device registers, I say go for it.  Maybe write 
to assembly too, to avoid the extra C overhead.  :)

More seriously, I'd like to start by analyzing what it would take to add 
multi-rail support over reliable-datagram endpoints, with the assumption that 
this would provide similar performance to what MPI could do.  This has the 
added benefit that it could work with completely different networks, though I'm 
not sure if that's a requirement.

I guess the first thing to figure out is how addressing works when multi-rail 
is in use.  Would we need some sort of super-address that's a union of the 
underlying fabric addresses?
_______________________________________________
ofiwg mailing list
[email protected]
http://lists.openfabrics.org/mailman/listinfo/ofiwg

Reply via email to