From: Jason Gunthorpe <jgg@nvidia.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Cc: "Christian König" <christian.koenig@amd.com>,
intel-xe@lists.freedesktop.org,
"Matthew Brost" <matthew.brost@intel.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Kasireddy Vivek" <vivek.kasireddy@intel.com>,
"Simona Vetter" <simona.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org
Subject: Re: [RFC PATCH v2 1/2] dma-buf: Add support for private interconnects
Date: Mon, 29 Sep 2025 13:13:54 -0300 [thread overview]
Message-ID: <20250929161354.GA2942991@nvidia.com> (raw)
In-Reply-To: <071c1bedd6fd902da9725c74c1b892c9fe76179c.camel@linux.intel.com>
On Mon, Sep 29, 2025 at 06:02:50PM +0200, Thomas Hellström wrote:
> > I'm not thinking about load balancing, more a 'quality of path'
> > metric.
>
> This sounds like it's getting increasingly complex. TBH I think that at
> least all fast interconnects we have in the planning for xe either are
> fine with falling back to the current pcie-p2p / dma-buf or in worst
> case system memory.
Yah, fallback is fine, but they will still want to prefer the better
paths if they are available. That's my point..
> The virtual interconnect we've been discussing
> would probably not be able to fall back at all unless negotiation gets
> somehow forwarded to the vm guest.
This is basically proposing to open code all the priority and QOR
matching in the drivers. I strongly think that will become
unmaintainable if things evolve in that direction..
What I'm suggesting is to have just enough infrastructure that we can
have the priority selection be in common code and implement the
simplest possible selection for right now. Run down the exports list
in order and the firt interconnect to match the importer's list is
selected.
All the more fancy stuff I've mentioned is someone else's problem down
the road to enhance the core matcher.
Jason
next prev parent reply other threads:[~2025-09-29 16:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 8:46 [RFC PATCH v2 0/2] dma-buf private interconnect POC Thomas Hellström
2025-09-26 8:46 ` [RFC PATCH v2 1/2] dma-buf: Add support for private interconnects Thomas Hellström
2025-09-26 12:56 ` Christian König
2025-09-26 13:51 ` Thomas Hellström
2025-09-26 14:41 ` Jason Gunthorpe
2025-09-26 14:51 ` Christian König
2025-09-26 16:00 ` Jason Gunthorpe
2025-09-29 8:16 ` Thomas Hellström
2025-09-29 8:20 ` Christian König
2025-09-29 8:25 ` Thomas Hellström
2025-09-29 12:27 ` Jason Gunthorpe
2025-09-29 8:16 ` Christian König
2025-09-29 12:45 ` Jason Gunthorpe
2025-09-29 16:02 ` Thomas Hellström
2025-09-29 16:13 ` Jason Gunthorpe [this message]
2025-09-26 8:46 ` [RFC PATCH v2 2/2] drm/xe/dma-buf: Add generic interconnect support framework Thomas Hellström
2025-09-26 9:34 ` ✗ CI.checkpatch: warning for dma-buf private interconnect POC (rev2) Patchwork
2025-09-26 9:35 ` ✓ CI.KUnit: success " Patchwork
2025-09-26 9:50 ` ✗ CI.checksparse: warning " Patchwork
2025-09-26 10:11 ` ✓ Xe.CI.BAT: success " Patchwork
2025-09-26 14:23 ` ✗ Xe.CI.Full: failure " Patchwork
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=20250929161354.GA2942991@nvidia.com \
--to=jgg@nvidia.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=simona.vetter@ffwll.ch \
--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