From: David Miller <[email protected]> Date: Wed, 01 Feb 2012 16:50:41 -0500 (EST)
> From: Roland Dreier <[email protected]> > Date: Wed, 1 Feb 2012 13:42:30 -0800 > >> OK. So do you have any thoughts about what the generic key available >> at transmit time (as you alluded to in your first message) might be? >> >> As far as I can figure things, it has to be something roughly >> equivalent to the neighbour, since it has to have the same type of >> information as what ARP/ND tells us. >> >> I guess I don't understand the on-demand lookup of the neigh. > > It's "inaddr_any(rt->rt_gateway) ? ip_hdr(skb)->daddr : rt->rt_gateway", > ie. the nexthop. That's the value we need to do proper on-demand > neigh lookups, it's the "daddr" argument to dst_lookup_neigh(). Actually, the argument is "&ip_hdr(skb)->daddr". So the crux of the matter is making sure we can get at the correct destination address in the packet header. Also we might have to conditionalize the code based upon protocol type, does ipoib handle ipv6? -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
