From: Jason Gunthorpe <jgg@nvidia.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Alistair Popple" <apopple@nvidia.com>,
"Karl Mehltretter" <kmehltretter@gmail.com>,
"Dongwon Kim" <dongwon.kim@intel.com>,
dri-devel@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
iommu@lists.linux.dev, "Kevin Tian" <kevin.tian@intel.com>,
"Leon Romanovsky" <leonro@nvidia.com>,
linaro-mm-sig@lists.linaro.org, linux-media@vger.kernel.org,
"Matthew Brost" <matthew.brost@intel.com>,
"Simona Vetter" <simona.vetter@ffwll.ch>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Vivek Kasireddy" <vivek.kasireddy@intel.com>
Subject: Re: [PATCH RFC 03/26] dma-buf: Add dma_buf_mapping_attach()
Date: Tue, 20 Oct 2026 11:31:15 -0300 [thread overview]
Message-ID: <20261020143115.GE3008132@nvidia.com> (raw)
In-Reply-To: <41bd4593-5918-4cda-922b-251805c25b60@amd.com>
On Tue, Oct 20, 2026 at 09:01:33AM +0200, Christian König wrote:
> > Like iommufd is not suddenly going to start understanding ualink after
> > an invalidation.
>
> Yeah but I think we can sort things out early on.
Yeah, if ther is some value thing can be excluded right from the
start.
> > Further, I had the (perhaps naive) expectation that the interconnect
> > option was not something that would change during mapping. I did not
> > think you would loose your PCIe option if ualink becomes available, or
> > vice versa. Though on deeper reflection I suppose someone could build
> > HW so you might loose your ualink option if the dmabuf is moved to
> > system memory while PCIe would still work.
>
> Yeah, that is definitely not correct.
>
> We have the clear requirement here that when one interconnect
> physically fails that we can still do things like let the work reach
> the next checkpoint, then it is taken of the HW, and the HW
> suspended for repair, then resumed and then work can continue....
>
> Similarly we have on the graphics side the requirement that physical
> placement can be moved to system memory because of some other device
> attaching, pinning for scanout or something suddenly requires the
> backing store to be contiguously allocated etc,,,
>
> So there are vast requirements that a buffer changes location when
> the mapping changes. I mean it is kind of pointless to have a
> feature like ODP to suspend your traffic if the underlying physical
> location of the memory can't change.
At least here, I am not aware of anyone actually using the ODP
capabilities to move and migrate memory. It seems by far and away the
most common use case is permanently pin things.
It seems like in these very complicated chips the placement of the
memory is a critical decision, if it moves around the performance is
so destroyed you may as well not bother.
I know this is not everyone and every use case, but it has been a bit
eye opening we built all this complex ODP stuf and I struggle to
justify it with an actual real user.
But yes, we should try to build it as you describe.
Thanks,
Jason
next prev parent reply other threads:[~2026-10-20 14:31 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 0:11 [PATCH RFC 00/26] Add DMA-buf mapping types and convert vfio/iommufd to use them Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 01/26] dma-buf: Introduce DMA-buf mapping types Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 02/26] dma-buf: Add the SGT DMA mapping type Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 03/26] dma-buf: Add dma_buf_mapping_attach() Jason Gunthorpe
2026-10-16 20:26 ` Karl Mehltretter
2026-10-19 8:35 ` Christian König
2026-10-19 12:43 ` Thomas Hellström
2026-10-19 13:30 ` Jason Gunthorpe
2026-10-19 13:47 ` Thomas Hellström
2026-10-19 15:34 ` Christian König
2026-10-19 18:41 ` Jason Gunthorpe
2026-10-20 7:01 ` Christian König
2026-10-20 14:31 ` Jason Gunthorpe [this message]
2026-02-18 0:11 ` [PATCH RFC 04/26] dma-buf: Route SGT related actions through attach->map_type Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 05/26] dma-buf: Allow single exporter drivers to avoid the match_mapping function Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 06/26] drm: Check the SGT ops for drm_gem_map_dma_buf() Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 07/26] dma-buf: Convert all the simple exporters to use SGT mapping type Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 08/26] drm/vmwgfx: Use match_mapping instead of dummy calls Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 09/26] accel/habanalabs: Use the SGT mapping type Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 10/26] drm/xe/dma-buf: " Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 11/26] drm/amdgpu: " Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 12/26] vfio/pci: Change the DMA-buf exporter to use mapping_type Jason Gunthorpe
2026-04-13 8:29 ` Baolu Lu
2026-04-13 13:01 ` Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 13/26] dma-buf: Update dma_buf_phys_vec_to_sgt() to use the SGT mapping type Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 14/26] iio: buffer: convert " Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 15/26] functionfs: " Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 16/26] dma-buf: Remove unused SGT stuff from the common structures Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 17/26] treewide: Rename dma_buf_map_attachment(_unlocked) to dma_buf_sgt_ Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 18/26] treewide: Rename dma_buf_unmap_attachment(_unlocked) to dma_buf_sgt_* Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 19/26] treewide: Rename dma_buf_attach() to dma_buf_sgt_attach() Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 20/26] treewide: Rename dma_buf_dynamic_attach() to dma_buf_sgt_dynamic_attach() Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 21/26] dma-buf: Add the Physical Address List DMA mapping type Jason Gunthorpe
2026-04-13 8:58 ` Christian König
2026-04-13 12:16 ` Jason Gunthorpe
2026-04-22 8:17 ` Christian König
2026-04-22 11:53 ` Jason Gunthorpe
2026-04-22 12:39 ` Christian König
2026-04-22 13:13 ` Jason Gunthorpe
2026-04-22 14:04 ` Christian König
2026-04-22 15:00 ` Jason Gunthorpe
2026-05-09 5:31 ` Xu Yilun
2026-05-11 22:48 ` Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 22/26] vfio/pci: Add physical address list support to DMABUF Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 23/26] iommufd: Use the PAL mapping type instead of a vfio function Jason Gunthorpe
2026-10-16 19:40 ` Karl Mehltretter
2026-02-18 0:11 ` [PATCH RFC 24/26] iommufd: Support DMA-bufs with multiple physical ranges Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 25/26] iommufd/selftest: Check multi-phys DMA-buf scenarios Jason Gunthorpe
2026-02-18 0:11 ` [PATCH RFC 26/26] dma-buf: Add kunit tests for mapping type Jason Gunthorpe
2026-03-01 19:05 ` [PATCH RFC 00/26] Add DMA-buf mapping types and convert vfio/iommufd to use them Jason Gunthorpe
2026-03-03 7:07 ` Kasireddy, Vivek
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=20261020143115.GE3008132@nvidia.com \
--to=jgg@nvidia.com \
--cc=apopple@nvidia.com \
--cc=christian.koenig@amd.com \
--cc=dongwon.kim@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=iommu@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=kmehltretter@gmail.com \
--cc=leonro@nvidia.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-media@vger.kernel.org \
--cc=matthew.brost@intel.com \
--cc=simona.vetter@ffwll.ch \
--cc=sumit.semwal@linaro.org \
--cc=thomas.hellstrom@linux.intel.com \
--cc=vivek.kasireddy@intel.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