From: "Stephen Bates" <sbates-pv7U853sEMVWk0Htik3J/w@public.gmane.org>
To: Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Logan Gunthorpe <logang-OTvnGxWRz7hWk0Htik3J/w@public.gmane.org>,
Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>,
Max Gurtovoy <maxg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [linux-rdma and rdma-core]: Unable to perform rdma_connect in loopbacked configuration
Date: Tue, 19 Sep 2017 01:11:49 +0000 [thread overview]
Message-ID: <AB27E7A4-FD5A-438E-A0CF-E593882F5EAE@raithlin.com> (raw)
In-Reply-To: <20170918205959.GC7059-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1084 bytes --]
>> 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?
> IIRC, you need to make 'ip route get blah' not return lo. This is done
> with some combination of policy routing and sysfs tweaking.
OK I think what Parav sent me aligns to that. I will test it and see if it works.
> 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âs not internal to one
NIC but across two NICs in the same server. Loopback inside one NIC works fine.
N§²æìr¸yúèØb²X¬¶Ç§vØ^)Þº{.nÇ+·¥{±Ù{ayº\x1dÊÚë,j\a¢f£¢·h»öì\x17/oSc¾Ú³9uÀ¦æåÈ&jw¨®\x03(éÝ¢j"ú\x1a¶^[m§ÿïêäz¹Þàþf£¢·h§~m
next prev parent reply other threads:[~2017-09-19 1:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 18:18 [linux-rdma and rdma-core]: Unable to perform rdma_connect in loopbacked configuration Stephen Bates
[not found] ` <59792242-F2C8-431A-BEDA-996844EDE4C5-pv7U853sEMVWk0Htik3J/w@public.gmane.org>
2017-09-18 19:09 ` Parav Pandit
[not found] ` <VI1PR0502MB3008FAC205874147558EA241D1630-o1MPJYiShExKsLr+rGaxW8DSnupUy6xnnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2017-09-18 19:41 ` Stephen Bates
2017-09-19 3:51 ` Leon Romanovsky
[not found] ` <20170919035134.GH5788-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-09-19 6:13 ` Parav Pandit
2017-09-18 20:59 ` Jason Gunthorpe
[not found] ` <20170918205959.GC7059-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-09-19 1:11 ` Stephen Bates [this message]
[not found] ` <AB27E7A4-FD5A-438E-A0CF-E593882F5EAE-pv7U853sEMVWk0Htik3J/w@public.gmane.org>
2017-09-20 16:28 ` Jason Gunthorpe
[not found] ` <20170920162828.GC536-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-09-26 20:52 ` Stephen Bates
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AB27E7A4-FD5A-438E-A0CF-E593882F5EAE@raithlin.com \
--to=sbates-pv7u853semvwk0htik3j/w@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=logang-OTvnGxWRz7hWk0Htik3J/w@public.gmane.org \
--cc=maxg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).