From: Jason Gunthorpe <jgg@nvidia.com>
To: Boshi Yu <boshiyu@linux.alibaba.com>
Cc: leon@kernel.org, linux-rdma@vger.kernel.org,
chengyou@linux.alibaba.com, kaishen@linux.alibaba.com
Subject: Re: [PATCH for-next v2 3/3] RDMA/erdma: Implement erdma_reg_user_mr_dmabuf
Date: Mon, 25 May 2026 13:37:08 -0300 [thread overview]
Message-ID: <20260525163708.GA2504127@nvidia.com> (raw)
In-Reply-To: <20260518120637.16831-4-boshiyu@linux.alibaba.com>
On Mon, May 18, 2026 at 08:06:28PM +0800, Boshi Yu wrote:
> + if (attr->flags & ERDMA_MEM_FLAG_DMABUF) {
> + umem_dmabuf = ib_umem_dmabuf_get_pinned(&dev->ibdev,
> + attr->start, attr->len,
> + attr->fd, attr->access);
> + if (IS_ERR(umem_dmabuf)) {
I don't want to see new MR implementations that use the get_pinned
interface.
Please implement the revoked interface Jacob added:
commit ff85a2ebacbdaec9f28c4660c991295ace93cd1c
Author: Jacob Moroni <jmoroni@google.com>
Date: Thu Mar 5 17:08:24 2026 +0000
RDMA/umem: Add pinned revocable dmabuf import interface
Added an interface for importing a pinned but revocable dmabuf.
This interface can be used by drivers that are capable of revocation
so that they can import dmabufs from exporters that may require it,
such as VFIO.
Any IBTA compliant device should be implement revoke at least through
regreg_mr.
Jason
prev parent reply other threads:[~2026-05-25 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 12:06 [PATCH for-next v2 0/3] RDMA/erdma: Add DMA-BUF memory registration Boshi Yu
2026-05-18 12:06 ` [PATCH for-next v2 1/3] RDMA/erdma: Rename get/put_mtt_entries to erdma_mem_init/uninit Boshi Yu
2026-05-18 12:06 ` [PATCH for-next v2 2/3] RDMA/erdma: Introduce struct erdma_mem_init_attr Boshi Yu
2026-05-18 12:06 ` [PATCH for-next v2 3/3] RDMA/erdma: Implement erdma_reg_user_mr_dmabuf Boshi Yu
2026-05-25 16:37 ` 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=20260525163708.GA2504127@nvidia.com \
--to=jgg@nvidia.com \
--cc=boshiyu@linux.alibaba.com \
--cc=chengyou@linux.alibaba.com \
--cc=kaishen@linux.alibaba.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.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