From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Wise Subject: Re: [PATCH v2] RDMA/CMA: fix iWARP adapter TCP port space usage Date: Wed, 23 Jun 2010 14:45:05 -0500 Message-ID: <4C226441.5000904@opengridcomputing.com> References: <4C225078.6050001@opengridcomputing.com> <4C225697.6060702@opengridcomputing.com> <20100623192909.GT4630@obsidianresearch.com> <4C2263B3.9010608@opengridcomputing.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C2263B3.9010608-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Jason Gunthorpe Cc: Roland Dreier , Bernard Metzler , "Tung, Chien Tin" , "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Peter P Waskiewicz Jr List-Id: linux-rdma@vger.kernel.org >> I wonder how does neighbor discovery, routing, etc work with iscsi? >> >> > > For cxgb3i: > > ND is handled by initiating ND via exported kernel services > (neigh_event_send()) and registering for NETEVENT_NEIGH_UPDATE net > events to get updated neigh entries. > > The host routing table is consulted via ip_route_output_flow() to map > a destination ip address to a local netdev, and then if that device is > T3, it will do the iscsi offload. > > By the way, this is how iWARP works too. The ND stuff is done by the IWCM during RESOLVE_ADDR. The routing lookups are done by the iWARP devices themselves typically. Steve. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html