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 15:13:36 -0500 Message-ID: <4C226AF0.8010505@opengridcomputing.com> References: <4C225078.6050001@opengridcomputing.com> <4C225697.6060702@opengridcomputing.com> <20100623192909.GT4630@obsidianresearch.com> <4C2263B3.9010608@opengridcomputing.com> <20100623195210.GU4630@obsidianresearch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Roland Dreier Cc: Jason Gunthorpe , 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 Roland Dreier wrote: > > Doesn't that mean the port collision problem still exits [for iSCSI], > > although probably less likely? > > Yes, it's there, but almost impossible to hit: first of all, iSCSI HBAs > never listen on a port, so that can never collide. Second, iSCSI HBAs > only establish connections to iSCSI targets on the iSCSI port -- so > really your only chance of a problem is if you ran an offloaded and > non-offloaded iSCSI initiator on the same IP to the same target, _and_ > you got unlucky on the local ports that you chose. So in practice no > one will hit this. > I believe, at least for cxgb3i, the ipaddr used is not bound to an ethX interface. So the 4-tuple will never collide with host TCP connections. -- 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