> > However, there's another problem with trying to lump address > > translation and connection into a single "connect" call, and this > > problem looks fundamental and fatal to me. The connect call takes a > > QP pointer, but to create a QP the consumer needs to know which local > > device to use. However, the consumer doesn't know which device to use > > until the destination address has been resolved to a route, including > > a local interface. > > The proposition, also presented (I beleive) in the OpenIB workshop, > include a function called ib_cma_get_device, that retrieves the device > (for qp creation purposes) according to the destination address and the > local routing table.
That function was included in the presentation. Given that the discussion focused on the proper location of address translation, it is understandable that its presence was overlooked. _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
