From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: [linux-rdma and rdma-core]: Unable to perform rdma_connect in loopbacked configuration Date: Wed, 20 Sep 2017 10:28:28 -0600 Message-ID: <20170920162828.GC536@obsidianresearch.com> References: <59792242-F2C8-431A-BEDA-996844EDE4C5@raithlin.com> <20170918205959.GC7059@obsidianresearch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Stephen Bates Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Logan Gunthorpe , Sagi Grimberg , Max Gurtovoy List-Id: linux-rdma@vger.kernel.org On Tue, Sep 19, 2017 at 01:11:49AM +0000, Stephen Bates wrote: > >> Using a NAT approach discussed in [1] I can setup IPv4 addresses on > >> both HCAs such that I avoid a local loopback (the addresses I use > >> are a little different to the ones in that reference but the > >> approach is identical). This allows ping, iperf and other IP based > >> applications to work just fine. For example: > > Thanks for the reply Jason > > > The RDMA stuff ignores everything in iptables. > > Can I ask why this is? roce is an incomplete emulation of the netstack with hardware offload. everything iptables is part of the incompleteness.. > > IMHO, it is also a bug if loopback roce doesn't just work out of the > > box, fully internally to the NIC. :\ > > OK. Note what I am trying to get working is a bit different. It'ss > not internal to one NIC but across two NICs in the same > server. Loopback inside one NIC works fine. I got that, but it makes no difference to my statement. Out of the box the kernel should select one of the two NICs and do internal loopback. That is consistent with the netstack semantic that the IP address is a property of the host not the netdev. Jason -- 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