>> Why include the connection protocol as part of the verbs >> layer? Granted I >> haven't looked at the iWarp specs in a long time, but I don't remember >> connection establishment being part of the verbs. > >Connection management is not part of the RDMAC verbs, however, we need >some >way for transports to "hook in" to the CM. The other approach is to have >a separate registration mechanism for connection management verbs, but >this seemed a little bizarre, so we just extended the provider verbs. > >Ideas?
I need to reacquaint myself with iWarp more, but I don't like the idea of adding CM calls as part of the verbs API, and in particular as part of a generic RDMA device structure. Does this suggest that each iWarp device driver will need to implement a connection establishment protocol? Isn't there a way to generalize that into a single iWarp CM module that can sit above multiple devices? How will connections between different devices be supported? I'm assuming that the Linux kernel will never permit an established connection to be offloaded onto a NIC. However it seems possible that a new iWarp connection could be done in a common way, with the result passed into the device through the modify QP call as the LLP stream. - 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
