Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: "Vivek Kasireddy" <vivek.kasireddy@intel.com>,
	dri-devel@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org,
	"Sumit Semwal" <sumit.semwal@linaro.org>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Simona Vetter" <simona.vetter@ffwll.ch>
Subject: Re: [RFC 1/8] dma-buf: Add support for map/unmap APIs for interconnects
Date: Tue, 28 Oct 2025 15:14:32 +0100	[thread overview]
Message-ID: <dcc1265b-be10-4a54-8eda-2f7be0e70371@amd.com> (raw)
In-Reply-To: <20251028140548.GJ1018328@nvidia.com>

On 10/28/25 15:05, Jason Gunthorpe wrote:
> On Tue, Oct 28, 2025 at 02:58:57PM +0100, Christian König wrote:
> 
>> Some kind of iterator like interface would be preferred where you
>> have first and next callbacks.
> 
> That's what I thought you were asking for..
> 
> Are you sure that is what you want? It will make mapping of fragments
> alot slower..

Well the first function should have a start parameter and both return offset and length.

Alternatively we could come up with some container, but yeah then we would need to convert into the container format again.

> 
>> Additional to that I'm not sure if the "interconnect" is a good
>> naming, essentially we want to use the new mapping functions to
>> replace the sg_table as well.
> 
> 'mapping type' ?

+1

Christian.> 
> Jason


  reply	other threads:[~2025-10-28 14:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14  7:08 [RFC 0/8] dma-buf: Add support for mapping dmabufs via interconnects Vivek Kasireddy
2025-10-14  7:08 ` [RFC 1/8] dma-buf: Add support for map/unmap APIs for interconnects Vivek Kasireddy
2025-10-20  9:34   ` Thomas Hellström
2025-10-21  5:45     ` Kasireddy, Vivek
2025-10-28 13:58   ` Christian König
2025-10-28 14:05     ` Jason Gunthorpe
2025-10-28 14:14       ` Christian König [this message]
2025-10-28 14:44         ` Jason Gunthorpe
2025-10-14  7:08 ` [RFC 2/8] dma-buf: Add a helper to match interconnects between exporter/importer Vivek Kasireddy
2025-10-17 15:58   ` Kasireddy, Vivek
2025-10-14  7:08 ` [RFC 3/8] dma-buf: Add support for IOV interconnect Vivek Kasireddy
2025-10-14  7:08 ` [RFC 4/8] vfio/pci/dmabuf: " Vivek Kasireddy
2025-10-14  7:08 ` [RFC 5/8] drm/xe/dma_buf: " Vivek Kasireddy
2025-10-14  7:08 ` [RFC 6/8] drm/xe/pf: Add a helper function to get a VF's backing object in LMEM Vivek Kasireddy
2025-10-14  7:08 ` [RFC 7/8] drm/xe/bo: Create new dma_addr array for dmabuf BOs associated with VFs Vivek Kasireddy
2025-10-14  7:08 ` [RFC 8/8] drm/xe/pt: Add an additional check for dmabuf BOs while doing bind Vivek Kasireddy

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=dcc1265b-be10-4a54-8eda-2f7be0e70371@amd.com \
    --to=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jgg@nvidia.com \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-media@vger.kernel.org \
    --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