From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Brost <matthew.brost@intel.com>, Jason Gunthorpe <jgg@ziepe.ca>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
leonro@nvidia.com, francois.dugast@intel.com,
himal.prasad.ghimiray@intel.com
Subject: Re: [PATCH v4 4/4] drm/pagemap: Use dma-map IOVA alloc, link, and sync API for DRM pagemap
Date: Mon, 16 Feb 2026 15:33:38 +0100 [thread overview]
Message-ID: <133fadf004fde9fe8a93b01bd6d282d52a838f6c.camel@linux.intel.com> (raw)
In-Reply-To: <aY+C5Qaik1XRZGwZ@lstrano-desk.jf.intel.com>
On Fri, 2026-02-13 at 12:00 -0800, Matthew Brost wrote:
> On Fri, Feb 13, 2026 at 10:56:46AM -0400, Jason Gunthorpe wrote:
> > On Wed, Feb 11, 2026 at 10:51:32AM -0800, Matthew Brost wrote:
> > > > So to be a little nicer on the IOVA allocator we could use the
> > > > below?
> > > >
> > > > dma_iova_try_alloc(dev, &state->dma_state,
> > > > (npages - i) *
> > > > PAGE_SIZE >=
> > > > HPAGE_PMD_SIZE ?
> > > > HPAGE_PMD_SIZE : 0,
> > > > (npages - i) *
> > > > PAGE_SIZE);
> > > >
> > >
> > > Yes, we can do that. No reason to force alignment if our copy
> > > code isn't
> > > going to try to use 2M GPU pages.
> >
> > When it comes to this I prefer we try to add alignment information
> > down to the iova allocator because I have other use cases for this
> > alignment optimization.
>
> Trying to parse this - what exactly is your preference here in the
> context of this patch?
>
> i.e., Is original code ok, is Thomas's suggestion ok, or should we do
> something entirely different?
>
> Matt
Interpreting this as Jason would want an alignment parameter to the
IOVA alloctor.
Although that's already the case, albeit somewhat awkwardly named.
Thanks,
Thomas
>
> >
> > Jason
next prev parent reply other threads:[~2026-02-16 14:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 4:19 [PATCH v4 0/4] Use new dma-map IOVA alloc, link, and sync API in GPU SVM and DRM pagemap Matthew Brost
2026-02-05 4:19 ` [PATCH v4 1/4] drm/pagemap: Add helper to access zone_device_data Matthew Brost
2026-02-05 4:19 ` [PATCH v4 2/4] drm/gpusvm: Use dma-map IOVA alloc, link, and sync API in GPU SVM Matthew Brost
2026-02-09 9:44 ` Thomas Hellström
2026-02-09 16:13 ` Matthew Brost
2026-02-09 16:41 ` Thomas Hellström
2026-02-05 4:19 ` [PATCH v4 3/4] drm/pagemap: Split drm_pagemap_migrate_map_pages into device / system Matthew Brost
2026-02-09 15:49 ` Thomas Hellström
2026-02-09 16:58 ` Matthew Brost
2026-02-09 17:09 ` Thomas Hellström
2026-02-05 4:19 ` [PATCH v4 4/4] drm/pagemap: Use dma-map IOVA alloc, link, and sync API for DRM pagemap Matthew Brost
2026-02-11 11:34 ` Thomas Hellström
2026-02-11 15:37 ` Matthew Brost
2026-02-11 18:48 ` Thomas Hellström
2026-02-11 18:51 ` Matthew Brost
[not found] ` <20260213145646.GO750753@ziepe.ca>
2026-02-13 20:00 ` Matthew Brost
2026-02-16 14:33 ` Thomas Hellström [this message]
2026-02-05 6:24 ` ✓ CI.KUnit: success for Use new dma-map IOVA alloc, link, and sync API in GPU SVM and DRM pagemap (rev4) Patchwork
2026-02-05 7:38 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-06 1:06 ` ✗ 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=133fadf004fde9fe8a93b01bd6d282d52a838f6c.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=francois.dugast@intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jgg@ziepe.ca \
--cc=leonro@nvidia.com \
--cc=matthew.brost@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