From: Jason Gunthorpe <jgg@ziepe.ca>
To: Zelong Yue <yuezelong@bytedance.com>
Cc: leon@kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] RDMA/core: Fix IPv6 loopback dst MAC address lookup logic
Date: Fri, 3 Jan 2025 11:31:43 -0400 [thread overview]
Message-ID: <20250103153143.GF26854@ziepe.ca> (raw)
In-Reply-To: <ab960175-d1f8-402e-9200-d47a7761315c@bytedance.com>
On Thu, Nov 28, 2024 at 05:21:42PM +0800, Zelong Yue wrote:
> 1. IPv6 addresses must be in the same subnet
> 2. The 'local' routing table must have lower priority than our custom policy
> routes
> 3. When IPv6 addresses are in different subnets, enabling RDMA loopback
> breaks TCP loopback
> functionality unless packet forwarding is enabled (which isn't feasible
> in our DC
> environment). We're still investigating a more elegant solution that
> wouldn't require
> packet forwarding or impact TCP loopback functionality.
What do you mean by packet forwarding?
For multi-NIC RDMA loopback to work the network must forward packets
externally from one NIC to another. Internal-to-the-node loopback is
not possible. If that forwarding works for RDMA I would expect it to
work for TCP too.
For single-NIC, I believe you can use lo to trigger an internal NIC
RDMA loopback as well.
In all cases TCP and RDMA traffic should be aligned, otherwise it
becomes impossible to use normal IP tools to debug the RDMA traffic.
> Given that RDMA loopback has different requirements from TCP/UDP
> loopback, maybe they should follow distinct routing logic.
It cannot, things must be consisent.
Jason
prev parent reply other threads:[~2025-01-03 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 12:35 yuezelong
2024-11-21 9:22 ` Zelong Yue
2024-11-21 13:53 ` Jason Gunthorpe
2024-11-28 9:21 ` Zelong Yue
2025-01-03 15:31 ` Jason Gunthorpe [this message]
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=20250103153143.GF26854@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=yuezelong@bytedance.com \
/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
all inboxes | Powered by JetHome®