From: "Yanjun.Zhu" <yanjun.zhu@linux.dev>
To: Shunsuke Mie <mie@igel.co.jp>
Cc: "Zhu Yanjun" <zyjzyj2000@gmail.com>,
"Christian König" <christian.koenig@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Doug Ledford" <dledford@redhat.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Jianxin Xiong" <jianxin.xiong@intel.com>,
"Leon Romanovsky" <leon@kernel.org>,
"Maor Gottlieb" <maorg@nvidia.com>,
"Sean Hefty" <sean.hefty@intel.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, dhobsong@igel.co.jp, taki@igel.co.jp,
etom@igel.co.jp
Subject: Re: [RFC PATCH v4 0/2] RDMA/rxe: Add dma-buf support
Date: Tue, 24 Feb 2026 09:37:27 -0800 [thread overview]
Message-ID: <a5f18c7c-dbde-4316-8444-bb198d890262@linux.dev> (raw)
In-Reply-To: <CANXvt5pcCsTegAkHkgvUnOkQ+eya0zHZh_KE=eUpXEubpyymRw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5071 bytes --]
On 2/24/26 1:17 AM, Shunsuke Mie wrote:
> Hi Zhu Yanjun,
>
> Thank you for reaching out and revisiting my 2021 proposal.
>
> Regarding the current status, I haven't been able to make much
> progress recently as other tasks have taken higher priority. However,
> I still believe this integration is important.
>
> From a technical perspective, as pointed out during the previous
> reviews, there were indeed issues with how dma_buf_map was being used.
> To address this in today's context, I believe we should transition to
> using iosys_map.
>
> I am still interested in this direction. While my current bandwidth is
> limited, I would welcome any collaboration—especially regarding the
> implementation of iosys_map support within rxe or the RDMA core.
Sorry. In the previous mail, there is a HTML part. It can not reach. As
such, I resend it.
DMABUF has become increasingly popular and is widely adopted across
various subsystems.
If we could also implement DMABUF support in rxe, it would significantly
enhance rxe’s usability and overall value.
Given your previous involvement in this area, it would be great to move
this forward in rxe.
I believe your expertise would be particularly helpful in driving the
implementation.
I’m happy to review and collaborate on the design and patches as needed.
Zhu Yanjun
>
> I'd be happy to discuss the technical details of this transition if
> you'd like to dive deeper.
>
> Best,
> Shunsuke Mie
>
>
> 2026年2月19日(木) 13:43 Zhu Yanjun <yanjun.zhu@linux.dev>:
>
> 在 2021/11/22 3:08, Shunsuke Mie 写道:
> > This patch series add a dma-buf support for rxe driver.
> >
> > A dma-buf based memory registering has beed introduced to use
> the memory
> > region that lack of associated page structures (e.g. device
> memory and CMA
> > managed memory) [1]. However, to use the dma-buf based memory,
> each rdma
> > device drivers require add some implementation. The rxe driver
> has not
> > support yet.
> >
> > [1] https://www.spinics.net/lists/linux-rdma/msg98592.html
> >
> > To enable to use the dma-buf memory in rxe rdma device, add some
> changes
> > and implementation in this patch series.
> >
> > This series consists of two patches. The first patch changes the
> IB core
> > to support for rdma drivers that has not dma device. The secound
> patch adds
> > the dma-buf support to rxe driver.
> >
> Hi, Shunsuke Mie
>
> I was revisiting your 2021 proposal around dma-buf integration
> with RDMA
> and the related discussions at the time.
>
> As you know, dma-buf usage in RDMA-related workflows has gained more
> traction recently, and we are seeing increasing interest in
> heterogeneous memory and cross-device buffer sharing. Given the
> changes
> in the ecosystem since then, I’m wondering whether you think the
> original direction might be worth reconsidering.
>
> Do you have any interest in continuing that line of work, or updating
> the design based on today’s context? If not, I’d still appreciate
> your
> perspective on what you see as the main blockers from the previous
> discussions, and whether you think the landscape has changed
> enough to
> justify another attempt.
>
> Depending on the direction, we may consider exploring dma-buf
> support in
> rxe or at the core level, but I’d prefer to first understand your
> view
> before moving forward.
>
> Zhu Yanjun
>
> > Related user space RDMA library changes are provided as a
> separate patch.
> >
> > v4:
> > * Fix warnings, unused variable and casting
> > v3: https://www.spinics.net/lists/linux-rdma/msg106776.html
> > * Rebase to the latest linux-rdma 'for-next' branch (5.15.0-rc6+)
> > * Fix to use dma-buf-map helpers
> > v2: https://www.spinics.net/lists/linux-rdma/msg105928.html
> > * Rebase to the latest linux-rdma 'for-next' branch (5.15.0-rc1+)
> > * Instead of using a dummy dma_device to attach dma-buf, just store
> > dma-buf to use software RDMA driver
> > * Use dma-buf vmap() interface
> > * Check to pass tests of rdma-core
> > v1: https://www.spinics.net/lists/linux-rdma/msg105376.html
> > * The initial patch set
> > * Use ib_device as dma_device.
> > * Use dma-buf dynamic attach interface
> > * Add dma-buf support to rxe device
> >
> > Shunsuke Mie (2):
> > RDMA/umem: Change for rdma devices has not dma device
> > RDMA/rxe: Add dma-buf support
> >
> > drivers/infiniband/core/umem_dmabuf.c | 20 ++++-
> > drivers/infiniband/sw/rxe/rxe_loc.h | 2 +
> > drivers/infiniband/sw/rxe/rxe_mr.c | 113
> ++++++++++++++++++++++++++
> > drivers/infiniband/sw/rxe/rxe_verbs.c | 34 ++++++++
> > include/rdma/ib_umem.h | 1 +
> > 5 files changed, 166 insertions(+), 4 deletions(-)
> >
>
[-- Attachment #2: Type: text/html, Size: 8144 bytes --]
prev parent reply other threads:[~2026-02-24 17:43 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 11:08 [RFC PATCH v4 0/2] RDMA/rxe: Add dma-buf support Shunsuke Mie
2021-11-22 11:08 ` Shunsuke Mie
2021-11-22 11:08 ` [RFC PATCH v4 1/2] RDMA/umem: Change for rdma devices has not dma device Shunsuke Mie
2021-11-22 11:08 ` Shunsuke Mie
2021-11-22 11:08 ` [RFC PATCH v4 2/2] RDMA/rxe: Add dma-buf support Shunsuke Mie
2021-11-22 11:08 ` Shunsuke Mie
2021-12-03 3:51 ` [RFC PATCH v4 0/2] " Shunsuke Mie
2021-12-03 3:51 ` Shunsuke Mie
2021-12-07 17:14 ` Jason Gunthorpe
2021-12-07 17:14 ` Jason Gunthorpe
2021-12-10 11:29 ` Shunsuke Mie
2021-12-10 11:29 ` Shunsuke Mie
2021-12-10 12:42 ` Jason Gunthorpe
2021-12-10 12:42 ` Jason Gunthorpe
2021-12-10 12:47 ` Christian König
2021-12-10 12:47 ` Christian König
2021-12-10 13:26 ` Jason Gunthorpe
2021-12-10 13:26 ` Jason Gunthorpe
2021-12-10 13:28 ` Christian König
2021-12-10 13:28 ` Christian König
2021-12-13 11:18 ` Shunsuke Mie
2021-12-13 11:18 ` Shunsuke Mie
2021-12-14 8:53 ` Christian König
2021-12-14 8:53 ` Christian König
2021-12-14 9:02 ` Shunsuke Mie
2021-12-14 9:02 ` Shunsuke Mie
2021-12-20 9:31 ` Daniel Vetter
2021-12-20 9:31 ` Daniel Vetter
2026-02-19 4:43 ` Zhu Yanjun
2026-02-24 9:17 ` Shunsuke Mie
2026-02-24 17:02 ` Zhu Yanjun
2026-02-24 17:37 ` Yanjun.Zhu [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=a5f18c7c-dbde-4316-8444-bb198d890262@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dhobsong@igel.co.jp \
--cc=dledford@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=etom@igel.co.jp \
--cc=jgg@ziepe.ca \
--cc=jianxin.xiong@intel.com \
--cc=leon@kernel.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=maorg@nvidia.com \
--cc=mie@igel.co.jp \
--cc=sean.hefty@intel.com \
--cc=sumit.semwal@linaro.org \
--cc=taki@igel.co.jp \
--cc=zyjzyj2000@gmail.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.