From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Chuck Lever <cel@kernel.org>, jgg@nvidia.com
Cc: Tom Talpey <tom@talpey.com>, Chuck Lever <chuck.lever@oracle.com>,
linux-rdma@vger.kernel.org, BMT@zurich.ibm.com
Subject: Re: [PATCH v3 0/4] Handle ARPHRD_NONE devices for siw
Date: Thu, 15 Jun 2023 19:59:24 +0800 [thread overview]
Message-ID: <ea05a59f-b13a-dfca-e7eb-4a873ea799ca@linux.dev> (raw)
In-Reply-To: <168675101993.2279.4985978457935843722.stgit@manet.1015granger.net>
在 2023/6/14 22:00, Chuck Lever 写道:
> Here's a series that implements support for siw on tunnel devices,
> based on suggestions from Jason Gunthorpe and Tom Talpey.
>
> This series does not address a similar issue with rxe because RoCE
> GID resolution behaves differently than it does for iWARP devices.
> An independent solution is likely to be required for rxe.
Thanks a lot for letting me know. Look forward to the independent
solution for rxe.
Zhu Yanjun
>
> Changes since v2:
> - Split into multiple patches
> - Pre-initialize gid_attr::ndev for iWARP devices
>
> ---
>
> Chuck Lever (4):
> RDMA/siw: Fabricate a GID on tun and loopback devices
> RDMA/core: Set gid_attr.ndev for iWARP devices
> RDMA/cma: Deduplicate error flow in cma_validate_port()
> RDMA/cma: Avoid GID lookups on iWARP devices
>
>
> drivers/infiniband/core/cache.c | 12 ++++++++++++
> drivers/infiniband/core/cma.c | 24 +++++++++++++++++++-----
> drivers/infiniband/sw/siw/siw.h | 1 +
> drivers/infiniband/sw/siw/siw_main.c | 22 ++++++++--------------
> drivers/infiniband/sw/siw/siw_verbs.c | 4 ++--
> 5 files changed, 42 insertions(+), 21 deletions(-)
>
> --
> Chuck Lever
>
next prev parent reply other threads:[~2023-06-15 12:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 14:00 [PATCH v3 0/4] Handle ARPHRD_NONE devices for siw Chuck Lever
2023-06-14 14:00 ` [PATCH v3 1/4] RDMA/siw: Fabricate a GID on tun and loopback devices Chuck Lever
2023-06-15 8:18 ` Bernard Metzler
2023-06-23 18:25 ` Tom Talpey
2023-06-14 14:00 ` [PATCH v3 2/4] RDMA/core: Set gid_attr.ndev for iWARP devices Chuck Lever
2023-06-23 18:37 ` Tom Talpey
2023-06-23 18:40 ` Chuck Lever III
2023-06-23 18:46 ` Tom Talpey
2023-06-14 14:00 ` [PATCH v3 3/4] RDMA/cma: Deduplicate error flow in cma_validate_port() Chuck Lever
2023-06-14 14:00 ` [PATCH v3 4/4] RDMA/cma: Avoid GID lookups on iWARP devices Chuck Lever
2023-06-22 15:13 ` Jason Gunthorpe
2023-06-23 17:02 ` Chuck Lever III
2023-06-23 17:12 ` Jason Gunthorpe
2023-06-15 11:59 ` Zhu Yanjun [this message]
2023-06-15 13:28 ` [PATCH v3 0/4] Handle ARPHRD_NONE devices for siw Chuck Lever III
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=ea05a59f-b13a-dfca-e7eb-4a873ea799ca@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=BMT@zurich.ibm.com \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=tom@talpey.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.