Caitlin Bestler wrote:
Any split in the API needs to allow iWARP providers to implement the first part as a nop. iWARP is defined on top of IP transports, and in fact frequently is cleanly layered over at least the IP layer (full clean separation from the TCP layer being a bit less common). So the iWARP implementation may literally have no access to ARP data.
If you look at the modified version of the API that I sent it, the iWarp implementation is limited to allocating a data structure, and copying the source and destination IP addresses. If a provider has a requirement to do something different they can.
- Sean _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
