From: Jason Gunthorpe <jgg@ziepe.ca>
To: Matthew Brost <matthew.brost@intel.com>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
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: Fri, 13 Feb 2026 10:56:46 -0400 [thread overview]
Message-ID: <20260213145646.GO750753@ziepe.ca> (raw)
In-Reply-To: <aYzPtCisUdv6FPEC@lstrano-desk.jf.intel.com>
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.
Jason
next prev parent reply other threads:[~2026-02-13 14:56 UTC|newest]
Thread overview: 18+ 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
2026-02-13 14:56 ` Jason Gunthorpe [this message]
2026-02-13 20:00 ` Matthew Brost
2026-02-16 14:33 ` Thomas Hellström
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=20260213145646.GO750753@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dri-devel@lists.freedesktop.org \
--cc=francois.dugast@intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=leonro@nvidia.com \
--cc=matthew.brost@intel.com \
--cc=thomas.hellstrom@linux.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