I agree with Mike's analysis. But I'd also like to point
out that even
when source compatability is not a requirement, source
familiarity
is. That is, even when recoding is feasible the API should
only
introduce new concepts as required to improve efficiency.
The
shift from socket model to QP/CQ is challenging enough as
is.
It's also where the benefit is. Changing how the
application
requests and accepts connections is just piling on more
things
for the developers to learn onto an already very full
plate, and
with nowhere near the same benefit.
The simple, IP/DNS-centric methods that Mike outlined
will
work on either iWARP or IB, and are very easily
understood
by those familiar with existing sockets/IP network
development.
The more complex models provide minor enhancements
for
very corner cases at the very heavy concept of requiring
the developer to understand a lot more about network
topology.
_______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
