>>From NetEffect's perspective, the per device approach is simple to >implement and I do not see it as an Ammasso specific approach. As Caitlin >described, existing code needs to be reorganized but this aspect of our port >is not a major effort.
I agree that connection setup code could be duplicated in all iWarp drivers to make such an interface work, but that doesn't necessarily make it the best approach. Personally, I would rather see a single iWarp connection manager establish the connections, and then hand those as the LLP handle to the modify QP verb. Based on comments, the iWarp vendors would prefer the host TCP stack establish connections. If this is the case, then why isn't having a single iWarp CM that resides above verbs preferred to duplicating that functionality in each driver? To me, this does sound like an Ammasso specific approach, in that they implemented TCP connections in hardware. Responses from NetEffect and Broadcom mentioned software solutions. - 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
