From: Edward Srouji <edwards@nvidia.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "Jason Gunthorpe" <jgg@ziepe.ca>,
"Leon Romanovsky" <leon@kernel.org>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org,
"Yishai Hadas" <yishaih@nvidia.com>
Subject: Re: [PATCH rdma-next v3 2/3] RDMA/uverbs: Add DMABUF object type and operations
Date: Mon, 23 Feb 2026 17:28:43 +0200 [thread overview]
Message-ID: <b1da71d7-3daf-4850-9239-fd3e2a946d95@nvidia.com> (raw)
In-Reply-To: <716e8a8e-e4e0-468d-9314-10082c2bbb8d@roeck-us.net>
On 2/23/2026 6:59 AM, Guenter Roeck wrote:
> External email: Use caution opening links or attachments
>
>
> On Sun, Feb 01, 2026 at 04:34:05PM +0200, Edward Srouji wrote:
>> From: Yishai Hadas <yishaih@nvidia.com>
>>
>> Expose DMABUF functionality to userspace through the uverbs interface,
>> enabling InfiniBand/RDMA devices to export PCI based memory regions
>> (e.g. device memory) as DMABUF file descriptors. This allows
>> zero-copy sharing of RDMA memory with other subsystems that support the
>> dma-buf framework.
>>
>> A new UVERBS_OBJECT_DMABUF object type and allocation method were
>> introduced.
>>
>> During allocation, uverbs invokes the driver to supply the
>> rdma_user_mmap_entry associated with the given page offset (pgoff).
>>
>> Based on the returned rdma_user_mmap_entry, uverbs requests the driver
>> to provide the corresponding physical-memory details as well as the
>> driver’s PCI provider information.
>>
>> Using this information, dma_buf_export() is called; if it succeeds,
>> uobj->object is set to the underlying file pointer returned by the
>> dma-buf framework.
>>
>> The file descriptor number follows the standard uverbs allocation flow,
>> but the file pointer comes from the dma-buf subsystem, including its own
>> fops and private data.
>>
>> When an mmap entry is removed, uverbs iterates over its associated
>> DMABUFs, marks them as revoked, and calls dma_buf_move_notify() so that
>> their importers are notified.
>>
>> The same procedure applies during the disassociate flow; final cleanup
>> occurs when the application closes the file.
>>
>> Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
>> Signed-off-by: Edward Srouji <edwards@nvidia.com>
>
> When trying to build powerpc:ppc64e_defconfig:
>
> ERROR: modpost: "dma_resv_wait_timeout" [drivers/infiniband/core/ib_core.ko] undefined!
> ERROR: modpost: "dma_buf_move_notify" [drivers/infiniband/core/ib_core.ko] undefined!
> ERROR: modpost: "dma_resv_reset_max_fences" [drivers/infiniband/core/ib_core.ko] undefined!
>
> The code now requires CONFIG_DMA_SHARED_BUFFER which is not enabled for
> this platform.
>
> Guenter
A fix was already sent, which I believe solves your issue:
https://lore.kernel.org/linux-rdma/20260216121213.2088910-1-arnd@kernel.org/
It adds 'select DMA_SHARED_BUFFER' to the infiniband Kconfig entry.
next prev parent reply other threads:[~2026-02-23 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 14:34 [PATCH rdma-next v3 0/3] RDMA: Add support for exporting dma-buf file descriptors Edward Srouji
2026-02-01 14:34 ` [PATCH rdma-next v3 1/3] RDMA/uverbs: Support external FD uobjects Edward Srouji
2026-02-01 14:34 ` [PATCH rdma-next v3 2/3] RDMA/uverbs: Add DMABUF object type and operations Edward Srouji
2026-02-23 4:59 ` Guenter Roeck
2026-02-23 15:28 ` Edward Srouji [this message]
2026-02-01 14:34 ` [PATCH rdma-next v3 3/3] RDMA/mlx5: Implement DMABUF export ops Edward Srouji
2026-02-05 12:58 ` [PATCH rdma-next v3 0/3] RDMA: Add support for exporting dma-buf file descriptors Leon Romanovsky
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=b1da71d7-3daf-4850-9239-fd3e2a946d95@nvidia.com \
--to=edwards@nvidia.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jgg@ziepe.ca \
--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=linux@roeck-us.net \
--cc=sumit.semwal@linaro.org \
--cc=yishaih@nvidia.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®