On Thu, 2005-09-29 at 09:59, Hal Rosenstock wrote: > On Wed, 2005-09-28 at 21:26, Sean Hefty wrote: > > Here's a first attempt at an API / implementation (that compiles only) for > > an address translation module for IB using ARP. The code should check the > > ARP cache for information, but is missing the actual ARP processing. > > Where would the path record lookup subsequent to the ARP go ? It would > be here as well prior to the connect, right ? > > > (We should be able to pull that from ib_at.) > > or sdp_link which has the more temporal netdev references currently :-) > > > The API is similar to the route > > portion of ib_at, but corrects issues with canceling requests. > > What are you referring to here ? > > > Only the destination IP address is required for input. > > > > The intent is that the CMA will use this service to locate the > > proper RDMA device GUID > > This is the outgoing device, right ? > > > and port to use in establishing a connection. > > Hopefully, this makes it clearer how I envision address translation wrt > > the CMA. > > When/if there are multiple paths, how is the selection performed ? > > Also, on the passive side, would a rdma_resolve_route also be done or > something else or wouldn't just a path lookup suffice here ? If it is > the latter, is that hidden under the rdma_accept or handled otherwise ?
A couple more comments about the emerging implementation for address translation: What happens if the destination IP address is a local one ? I think there is some missing code here. Also, shouldn't non subnet local destination IP addresses be handled ? -- Hal _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
