<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Ok thanks. I'll look at these see what is different.<br>
<br>
Leo Tominna<br>
<br>
On 7/13/2009 2:14 PM, Jason Gunthorpe wrote:
<blockquote cite="mid:20090713211447.GC21867@obsidianresearch.com"
type="cite">
<pre wrap="">On Mon, Jul 13, 2009 at 01:35:08PM -0700, <a class="moz-txt-link-abbreviated" href="mailto:leo.tominna@oracle.com">leo.tominna@oracle.com</a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Right, there should only be one route lookup call. And the send_arp should
match what TCP/UDP are doing, I'm pretty sure they don't use neigh_event_send
like ib_addr is, or if they do, they are not using ip_route_output_key to get
the neighbor entry. I could not find the code that generates arps for these
protocols.
</pre>
</blockquote>
<pre wrap=""><!---->
They do, but indirectly, dst_output() cals neigh_resolve_output()
which calls neigh_event_send() - since there is no real skb in the RDMA
routines it seems reasonable to call neigh_event_sent() directly..
ip_route_output_key is used to populate dst in the skb which is
fetched by neigh_resolve_output to get the neigh and the neigh has the
ofid.
Jason
</pre>
</blockquote>
</body>
</html>