From: Matthew Brost <matthew.brost@intel.com>
To: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
"Carlos Santa" <carlos.santa@intel.com>,
"Ryan Neph" <ryanneph@google.com>,
"Christian Koenig" <christian.koenig@amd.com>,
"Huang Rui" <ray.huang@amd.com>,
"Matthew Auld" <matthew.auld@intel.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
linux-kernel@vger.kernel.org,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: Re: [PATCH v3 03/33] drm/ttm: Record sub-optimal page order allocations in ttm_tt
Date: Fri, 6 Nov 2026 12:06:17 -0800 [thread overview]
Message-ID: <au4zOQ0X2Lq+PsZB@gsse-cloud1.jf.intel.com> (raw)
In-Reply-To: <au08wNRON0_b5wuG@nvishwa1-desk>
On Thu, Nov 05, 2026 at 06:34:40PM -0800, Niranjana Vishwanathapura wrote:
> On Fri, Jul 10, 2026 at 07:55:49PM -0700, Matthew Brost wrote:
> > When __ttm_pool_alloc() fails to allocate a chunk at the device's
> > beneficial order and falls back to a smaller order, the object ends up
> > backed by a sub-optimal set of pages. Nothing currently records this, so
> > a driver has no way to know an object would benefit from being re-backed
> > with beneficial-order pages later.
> >
> > Add TTM_TT_FLAG_BENEFICIAL_ORDER_FAILED to struct ttm_tt page_flags,
> > cleared at the start of every fresh allocation (in both ttm_pool_alloc()
> > and ttm_pool_restore_and_alloc()). Set it in __ttm_pool_alloc() when an
> > allocation at exactly the beneficial order fails before dropping to a
> > lower order.
> >
> > Drivers can use this hint to queue the buffer object for later
> > defragmentation.
> >
> > Cc: Carlos Santa <carlos.santa@intel.com>
> > Cc: Ryan Neph <ryanneph@google.com>
> > Cc: Christian Koenig <christian.koenig@amd.com>
> > Cc: Huang Rui <ray.huang@amd.com>
> > Cc: Matthew Auld <matthew.auld@intel.com>
> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> > Cc: Maxime Ripard <mripard@kernel.org>
> > Cc: Thomas Zimmermann <tzimmermann@suse.de>
> > Cc: David Airlie <airlied@gmail.com>
> > Cc: Simona Vetter <simona@ffwll.ch>
> > Cc: dri-devel@lists.freedesktop.org
> > Cc: linux-kernel@vger.kernel.org
> > Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> > Assisted-by: GitHub_Copilot:claude-opus-4.8
> > Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> > ---
> > drivers/gpu/drm/ttm/ttm_pool.c | 13 +++++++++++++
> > include/drm/ttm/ttm_tt.h | 24 +++++++++++++++++++++++-
> > 2 files changed, 36 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/ttm/ttm_pool.c b/drivers/gpu/drm/ttm/ttm_pool.c
> > index 5b7d7f5ae53d..e9175c0290d7 100644
> > --- a/drivers/gpu/drm/ttm/ttm_pool.c
> > +++ b/drivers/gpu/drm/ttm/ttm_pool.c
> > @@ -796,6 +796,7 @@ static int __ttm_pool_alloc(struct ttm_pool *pool, struct ttm_tt *tt,
> > struct ttm_pool_alloc_state *alloc,
> > struct ttm_pool_tt_restore *restore)
> > {
> > + const unsigned int beneficial_order = ttm_pool_beneficial_order(pool);
> > enum ttm_caching page_caching;
> > gfp_t gfp_flags = GFP_USER;
> > pgoff_t caching_divide;
> > @@ -846,6 +847,16 @@ static int __ttm_pool_alloc(struct ttm_pool *pool, struct ttm_tt *tt,
> > /* If that fails, lower the order if possible and retry. */
> > if (!p) {
> > if (order) {
> > + /*
> > + * Failing to allocate at the device's beneficial
> > + * order means we are about to back this object
> > + * with a sub-optimal (smaller order) set of
> > + * pages. Record it so the driver can later try to
> > + * defragment the object back to beneficial order.
> > + */
> > + if (beneficial_order && order == beneficial_order)
> > + tt->page_flags |=
> > + TTM_TT_FLAG_BENEFICIAL_ORDER_FAILED;
>
> I haven't looked at beneficial_reclaim_backoff usecase yet, but this flag
> gets set irrespective of whether the allocation failure resulted with/without
> the beneficial_reclaim_backoff request from the driver. Is that intended?
>
Yes. The end goal (the series on list needs a slight Xe side tweak) it
everything in the foreground (new memory allocations, swapin after
shrinking, etc..) sets beneficial_reclaim_backoff (no reclaim). In that
case if we don't get optimial pages, the defragmenter in the background
does aggresive reclaim and then prunes in pages it finds at
beneficial_order in a way we don't miss page flips.
Matt
> Other than that, the change here LGTM, though I still need to look at how driver uses
> this flag in more detail.
>
> Niranjana
>
> > --order;
> > page_caching = tt->caching;
> > allow_pools = true;
> > @@ -910,6 +921,7 @@ int ttm_pool_alloc(struct ttm_pool *pool, struct ttm_tt *tt,
> > if (WARN_ON(ttm_tt_is_backed_up(tt)))
> > return -EINVAL;
> >
> > + tt->page_flags &= ~TTM_TT_FLAG_BENEFICIAL_ORDER_FAILED;
> > ttm_pool_alloc_state_init(tt, &alloc);
> >
> > return __ttm_pool_alloc(pool, tt, ctx, &alloc, NULL);
> > @@ -942,6 +954,7 @@ int ttm_pool_restore_and_alloc(struct ttm_pool *pool, struct ttm_tt *tt,
> > if (!restore) {
> > gfp_t gfp = GFP_KERNEL | __GFP_NOWARN;
> >
> > + tt->page_flags &= ~TTM_TT_FLAG_BENEFICIAL_ORDER_FAILED;
> > ttm_pool_alloc_state_init(tt, &alloc);
> > if (ctx->gfp_retry_mayfail)
> > gfp |= __GFP_RETRY_MAYFAIL;
> > diff --git a/include/drm/ttm/ttm_tt.h b/include/drm/ttm/ttm_tt.h
> > index 406437ad674b..ce7533677d77 100644
> > --- a/include/drm/ttm/ttm_tt.h
> > +++ b/include/drm/ttm/ttm_tt.h
> > @@ -90,6 +90,14 @@ struct ttm_tt {
> > * TTM_TT_FLAG_BACKED_UP: TTM internal only. This is set if the
> > * struct ttm_tt has been (possibly partially) backed up.
> > *
> > + * TTM_TT_FLAG_BENEFICIAL_ORDER_FAILED: Set by the TTM pool allocator
> > + * when at least one chunk that could have been allocated at the pool's
> > + * beneficial order had to fall back to a smaller order. This indicates
> > + * that a sub-optimal set of pages was chosen for this object, and can
> > + * be used by drivers to queue the buffer object for later
> > + * defragmentation. Drivers should access this via the
> > + * ttm_tt_is_beneficial_order_failed() helper.
> > + *
> > * TTM_TT_FLAG_PRIV_POPULATED: TTM internal only. DO NOT USE. This is
> > * set by TTM after ttm_tt_populate() has successfully returned, and is
> > * then unset when TTM calls ttm_tt_unpopulate().
> > @@ -101,8 +109,9 @@ struct ttm_tt {
> > #define TTM_TT_FLAG_EXTERNAL_MAPPABLE BIT(3)
> > #define TTM_TT_FLAG_DECRYPTED BIT(4)
> > #define TTM_TT_FLAG_BACKED_UP BIT(5)
> > +#define TTM_TT_FLAG_BENEFICIAL_ORDER_FAILED BIT(6)
> >
> > -#define TTM_TT_FLAG_PRIV_POPULATED BIT(6)
> > +#define TTM_TT_FLAG_PRIV_POPULATED BIT(7)
> > uint32_t page_flags;
> > /** @num_pages: Number of pages in the page array. */
> > uint32_t num_pages;
> > @@ -179,6 +188,19 @@ static inline void ttm_tt_clear_backed_up(struct ttm_tt *tt)
> > tt->page_flags &= ~TTM_TT_FLAG_BACKED_UP;
> > }
> >
> > +/**
> > + * ttm_tt_is_beneficial_order_failed() - Whether the tt is backed at a
> > + * sub-optimal page order
> > + * @tt: The struct ttm_tt.
> > + *
> > + * Return: true if the pool allocator had to fall back below the pool's
> > + * beneficial order when backing this tt, false otherwise.
> > + */
> > +static inline bool ttm_tt_is_beneficial_order_failed(const struct ttm_tt *tt)
> > +{
> > + return tt->page_flags & TTM_TT_FLAG_BENEFICIAL_ORDER_FAILED;
> > +}
> > +
> > /**
> > * ttm_tt_create
> > *
> > --
> > 2.34.1
> >
next prev parent reply other threads:[~2026-11-06 20:06 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 2:55 [PATCH v3 00/33] drm/ttm, drm/xe: Minimize dma-resv hold times and defragment sub-optimally backed BOs Matthew Brost
2026-07-11 2:55 ` [PATCH v3 01/33] drm/ttm/pool: Allow backing off reclaim at the beneficial order Matthew Brost
2026-11-06 2:55 ` Niranjana Vishwanathapura
2026-07-11 2:55 ` [PATCH v3 02/33] drm/ttm/pool: Add ttm_pool_page_order_nodma() helper Matthew Brost
2026-11-05 11:27 ` Matthew Auld
2026-11-06 2:30 ` Niranjana Vishwanathapura
2026-07-11 2:55 ` [PATCH v3 03/33] drm/ttm: Record sub-optimal page order allocations in ttm_tt Matthew Brost
2026-11-06 2:34 ` Niranjana Vishwanathapura
2026-11-06 20:06 ` Matthew Brost [this message]
2026-07-11 2:55 ` [PATCH v3 04/33] drm/ttm: Introduce ttm_pool_alloc_iter for __ttm_pool_alloc() Matthew Brost
2026-11-06 2:39 ` Niranjana Vishwanathapura
2026-07-11 2:55 ` [PATCH v3 05/33] drm/ttm: Support defragmentation moves Matthew Brost
2026-11-06 2:51 ` Niranjana Vishwanathapura
2026-07-11 2:55 ` [PATCH v3 06/33] drm/ttm: Add fault injection for beneficial-order allocation failures Matthew Brost
2026-11-06 2:54 ` Niranjana Vishwanathapura
2026-07-11 2:55 ` [PATCH v3 07/33] drm/ttm: Harvest beneficial-order pages on defragmentation moves Matthew Brost
2026-07-11 2:55 ` [PATCH v3 08/33] drm/ttm: Bound page (re)allocation per defragmentation move Matthew Brost
2026-07-11 2:55 ` [PATCH v3 09/33] drm/ttm: Preallocate beneficial-order defrag pages outside the lock Matthew Brost
2026-07-11 2:55 ` [PATCH v3 10/33] drm/ttm: Add full out-of-lock preallocation for ttm_pool_alloc() Matthew Brost
2026-07-11 2:56 ` [PATCH v3 15/33] drm/xe: Track BOs backed at a sub-optimal page order Matthew Brost
2026-11-07 4:49 ` Niranjana Vishwanathapura
2026-07-11 2:56 ` [PATCH v3 16/33] drm/xe: Back off beneficial-order reclaim under defrag pressure Matthew Brost
2026-11-07 5:02 ` Niranjana Vishwanathapura
2026-07-11 2:56 ` [PATCH v3 17/33] drm/xe: Add xe_migrate_copy_defrag() for on-GPU defrag copies Matthew Brost
2026-11-03 12:58 ` Matthew Auld
2026-11-03 20:08 ` Matthew Brost
2026-11-04 12:37 ` Matthew Auld
2026-11-07 5:07 ` Niranjana Vishwanathapura
2026-07-11 2:56 ` [PATCH v3 18/33] drm/xe: Handle defrag moves in xe_bo_move() Matthew Brost
2026-11-07 5:12 ` Niranjana Vishwanathapura
2026-07-11 2:56 ` [PATCH v3 19/33] drm/xe: Skip self-copies for borrowed pages on defrag moves Matthew Brost
2026-07-11 2:56 ` [PATCH v3 20/33] drm/xe: Add a page defragmentation worker Matthew Brost
2026-11-07 5:27 ` Niranjana Vishwanathapura
2026-07-11 2:56 ` [PATCH v3 21/33] drm/xe: Add defrag GT stats Matthew Brost
2026-07-11 2:56 ` [PATCH v3 22/33] drm/xe: Add Kconfig.profile options for BO defrag configuration Matthew Brost
2026-07-11 2:56 ` [PATCH v3 23/33] drm/xe: Defrag using out-of-lock page preallocation Matthew Brost
2026-07-11 2:56 ` [PATCH v3 24/33] drm/xe: Add defrag profiling tracepoints Matthew Brost
2026-07-11 2:56 ` [PATCH v3 25/33] drm/xe: Preallocate system BO backing outside the dma-resv lock Matthew Brost
2026-07-11 2:56 ` [PATCH v3 26/33] drm/xe: Add tracepoint for xe_gem_create_ioctl Matthew Brost
2026-07-11 2:56 ` [PATCH v3 27/33] drm/xe: Add IOVA-based xe_res_cursor variant Matthew Brost
2026-11-04 12:23 ` Matthew Auld
2026-07-11 2:56 ` [PATCH v3 28/33] drm/xe: Use IOVA-based DMA mapping for eligible tt BOs Matthew Brost
2026-11-03 19:00 ` Matthew Auld
2026-11-03 20:21 ` Matthew Brost
2026-11-04 11:39 ` Matthew Auld
2026-11-05 3:04 ` Matthew Brost
2026-07-11 2:56 ` [PATCH v3 29/33] drm/xe: Add per-device dependency scheduler for IOVA defrag finalize Matthew Brost
2026-07-11 2:56 ` [PATCH v3 30/33] drm/xe: Add packed copy-step IOVA mapping for defrag Matthew Brost
2026-07-11 2:56 ` [PATCH v3 31/33] drm/xe: Blit src-natural to dst-packed for defrag-IOVA copies Matthew Brost
2026-07-11 2:56 ` [PATCH v3 32/33] drm/xe: Finalize defrag-IOVA moves with post-copy job Matthew Brost
2026-07-11 2:56 ` [PATCH v3 33/33] drm/amdgpu: Preallocate system BO pages outside the reservation lock Matthew Brost
2026-07-11 10:46 ` Christian König
2026-07-13 20:24 ` Matthew Brost
2026-07-14 9:17 ` Christian König
2026-07-14 15:15 ` Matthew Brost
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=au4zOQ0X2Lq+PsZB@gsse-cloud1.jf.intel.com \
--to=matthew.brost@intel.com \
--cc=airlied@gmail.com \
--cc=carlos.santa@intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.auld@intel.com \
--cc=mripard@kernel.org \
--cc=niranjana.vishwanathapura@intel.com \
--cc=ray.huang@amd.com \
--cc=ryanneph@google.com \
--cc=simona@ffwll.ch \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®