From: Leon Romanovsky <leon@kernel.org>
To: "D. Wythe" <alibuda@linux.alibaba.com>
Cc: mjambigi@linux.ibm.com, wenjia@linux.ibm.com,
wintera@linux.ibm.com, dust.li@linux.alibaba.com,
tonylu@linux.alibaba.com, guwen@linux.alibaba.com,
kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org,
pabeni@redhat.com, edumazet@google.com, sidraya@linux.ibm.com,
jaka@linux.ibm.com
Subject: Re: [PATCH net-next v2] net/smc: add full IPv6 support for SMC
Date: Tue, 28 Oct 2025 14:31:01 +0200 [thread overview]
Message-ID: <20251028123101.GR12554@unreal> (raw)
In-Reply-To: <20251028095450.GA38488@j66a10360.sqa.eu95>
On Tue, Oct 28, 2025 at 05:54:50PM +0800, D. Wythe wrote:
> On Mon, Oct 27, 2025 at 03:42:27PM +0200, Leon Romanovsky wrote:
> > On Wed, Oct 22, 2025 at 11:23:09AM +0800, D. Wythe wrote:
> > > The current SMC implementation is IPv4-centric. While it contains a
> > > workaround for IPv4-mapped IPv6 addresses, it lacks a functional path
> > > for native IPv6, preventing its use in modern dual-stack or IPv6-only
> > > networks.
> > >
> > > This patch introduces full, native IPv6 support by refactoring the
> > > address handling mechanism to be IP-version agnostic, which is
> > > achieved by:
> > >
> > > - Introducing a generic `struct smc_ipaddr` to abstract IP addresses.
> > > - Implementing an IPv6-specific route lookup function.
> > > - Extend GID matching logic for both IPv4 and IPv6 addresses
> > >
> > > With these changes, SMC can now discover RDMA devices and establish
> > > connections over both native IPv4 and IPv6 networks.
> >
> > Why can't you use rdma-cm in-kernel API like any other in-kernel RDMA consumers?
> >
> > Thanks
> >
> > >
>
> Hi Leon,
>
> Regarding RDMA-CM, I’m not sure if I’ve fully grasped your point, but
> based on my current understanding, I believe SMC cannot use RDMA-CM.
> There are a few reasons for this:
>
> Firstly, SMC is designed to work not only with RDMA devices but also
> needs to negotiate with DIBS(DIRECT INTERNAL BUFFER SHARING) devices. This
> means we must support scenarios where no RDMA device is present.
> Therefore, we require a round of out-of-band negotiation regardless of
> the final device choice. In this context, even if we ultimately select
> an RDMA device, using rdma-cm to establish the connection would be
> redundant.
Ahh, yes, I always failed to remember this.
Thanks
>
> Additionally, SMC requires multiplexing multiple connections over a
> single QP. We need to decide during the out-of-band negotiation which
> specific QP to reuse for the connection. From what I know, rdma-cm does
> not seem to offer this capability either.
>
> Best regards,
> D. Wythe
>
prev parent reply other threads:[~2025-10-28 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 3:23 [PATCH net-next v2] net/smc: add full IPv6 support for SMC D. Wythe
2025-10-23 1:34 ` Dust Li
2025-10-28 10:18 ` D. Wythe
2025-10-27 13:42 ` Leon Romanovsky
2025-10-28 9:54 ` D. Wythe
2025-10-28 12:31 ` Leon Romanovsky [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=20251028123101.GR12554@unreal \
--to=leon@kernel.org \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=jaka@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjambigi@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sidraya@linux.ibm.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.com \
--cc=wintera@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).