The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Zhaoyu Liu" <liuzhaoyu.zackary@picoheart.com>
To: "Arunpravin Paneer Selvam" <arunpravin.paneerselvam@amd.com>
Cc: "matthew.auld" <matthew.auld@intel.com>,
	 "joelagnelf" <joelagnelf@nvidia.com>,
	"airlied" <airlied@gmail.com>,  "simona" <simona@ffwll.ch>,
	<francois.dugast@intel.com>,
	 "dri-devel" <dri-devel@lists.freedesktop.org>,
	 "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] gpu: buddy: avoid repeated builds of root dfs when alloc range
Date: Mon, 13 Jul 2026 21:25:33 +0800	[thread overview]
Message-ID: <alTnTUq456b3Pf5d@hostpc> (raw)
In-Reply-To: <4901dc21-c281-4e60-b2a2-061100a5c8a9@amd.com>

On Mon, Jul 13, 2026 at 01:32:22PM +0530, Arunpravin Paneer Selvam wrote:
> 
> 
> On 7/13/2026 12:01 PM, 刘照玉 wrote:
> > [You don't often get email from liuzhaoyu.zackary@picoheart.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
> > 
> > Please help review this patch.
> > Thanks!
> I was wondering whether this optimization provides a measurable benefit in
> practice. Since mm->n_roots is typically quite small, the previous DFS list
> construction only adds a few list_add_tail() operations per allocation.
> On the other hand, the new approach introduces an additional helper call and
> branching during candidate selection. Have you done any profiling or
> benchmarking to quantify the improvement?
> 
> Thanks,
> Arun.

Thank you for your review, Arun.

To verify the gain, a KUnit perf case (gpu_test_buddy_range_alloc_perf)
was added locally. It sweeps fixed 1MB bias ranges across the whole
address space, allocating and freeing each range exactly, repeated
10000 iterations.

Two scenarios cover the two extremes of n_roots:
- 16MB mm  -> n_roots = 1  (16 bias ranges)
- 1GB-1 mm -> n_roots = 18 (1023 bias ranges)

Each configuration was measured 3 times and averaged. Three builds were
compared:
- baseline  : unmodified tree
- no-inline : patched, __get_candidate_block is static
- inline    : patched, __get_candidate_block is static inline

+----------+-----------------+------------------+------------------+
| mm_size  |  baseline (ns)  | no-inline (ns)   | inline (ns)      |
|          |                 | (change vs base) | (change vs base) |
+----------+-----------------+------------------+------------------+
| 16MB     |          66877  |     66598        |     64663        |
|          |                 |     -0.42%       |     -3.31%       |
+----------+-----------------+------------------+------------------+
| 1GB-1    |        9333559  |   9193052        |   9251951        |
|          |                 |     -1.51%       |     -0.87%       |
+----------+-----------------+------------------+------------------+

And, I've sent new v2 patch with inline function,
link: https://lore.kernel.org/all/alTlW8TmTXLocWKP@hostpc/

Please help review it again.

Thanks,
zackary

> > 
> > > From: "Zhaoyu Liu"<liuzhaoyu.zackary@picoheart.com>
> > > Date:  Thu, Jul 9, 2026, 19:20
> > > Subject:  [PATCH] gpu: buddy: avoid repeated builds of root dfs when alloc range
> > > To: <matthew.auld@intel.com>, <arunpravin.paneerselvam@amd.com>, <joelagnelf@nvidia.com>, <airlied@gmail.com>, <simona@ffwll.ch>
> > > Cc: <dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
> > > The buddy allocator previously pre-built a DFS list by inserting all
> > > root blocks via list_add_tail() before every allocation call in
> > > __alloc_range_bias() and __gpu_buddy_alloc_range(). This is wasteful
> > > when the allocation can be satisfied by the first root or by sub-blocks
> > > produced from splits, as the remaining roots are never consumed.
> > > Introduce __get_candidate_block() which unifies the block acquisition
> > > logic for both __alloc_range_bias() and __alloc_range(): it first
> > > checks the DFS list (populated by splits during allocation or
> > > pre-filled by the caller for trim), and only when the list is exhausted
> > > does it lazily fetch the next root block through a cursor.
> > > When the caller pre-fills the DFS list (trim scenario), the cursor is
> > > initialized to mm->n_roots to disable root iteration entirely,
> > > preserving the original behavior.
> > > Signed-off-by: Zhaoyu Liu <liuzhaoyu.zackary@picoheart.com>
> > > ---
> > >   drivers/gpu/buddy.c | 61 ++++++++++++++++++++++++++++++---------------
> > >   1 file changed, 41 insertions(+), 20 deletions(-)
> > > diff --git a/drivers/gpu/buddy.c b/drivers/gpu/buddy.c
> > > index dc81fe0301ce..2cebb87020c7 100644
> > > --- a/drivers/gpu/buddy.c
> > > +++ b/drivers/gpu/buddy.c
> > > @@ -700,6 +700,41 @@ static void __gpu_buddy_undo_splits(struct gpu_buddy *mm,
> > >           }
> > >   }
> > > 
> > > +/**
> > > + * __get_candidate_block - Get a candidate block for allocation.
> > > + * @mm: GPU buddy manager
> > > + * @dfs: List of candidate blocks. Populated in two ways: (1) pre-filled by
> > > + *       the caller before allocation with blocks available for allocation,
> > > + *       and (2) extended during allocation by block splits, which add the
> > > + *       resulting sub-blocks for subsequent finer-grained allocation.
> > > + * @cursor: Pointer to current root index, advanced when iterating roots.
> > > + *          Pass in a value >= mm->n_roots to disable root iteration entirely,
> > > + *          restricting block acquisition to @dfs only; this is used in the
> > > + *          trim scenario where only pre-split sub-blocks should be considered.
> > > + *
> > > + * Return: Pointer to the acquired block on success, ERR_PTR(-ENOSPC) when no
> > > + * more blocks are available.
> > > + */
> > > +static struct gpu_buddy_block*
> > > +__get_candidate_block(struct gpu_buddy *mm, struct list_head *dfs,
> > > +                uint32_t *cursor)
> > > +{
> > > +        struct gpu_buddy_block *block;
> > > +
> > > +        block = list_first_entry_or_null(dfs,
> > > +                                        struct gpu_buddy_block,
> > > +                                        tmp_link);
> > > +        if (block) {
> > > +                list_del(&block->tmp_link);
> > > +                return block;
> > > +        }
> > > +
> > > +        if (*cursor >= mm->n_roots)
> > > +                return ERR_PTR(-ENOSPC);
> > > +
> > > +        return mm->roots[(*cursor)++];
> > > +}
> > > +
> > >   static struct gpu_buddy_block *
> > >   __alloc_range_bias(struct gpu_buddy *mm,
> > >                      u64 start, u64 end,
> > > @@ -711,25 +746,18 @@ __alloc_range_bias(struct gpu_buddy *mm,
> > >           struct gpu_buddy_block *block;
> > >           LIST_HEAD(dfs);
> > >           int err;
> > > -        int i;
> > > +        uint32_t cursor = 0;
> > > 
> > >           end = end - 1;
> > > 
> > > -        for (i = 0; i < mm->n_roots; ++i)
> > > -                list_add_tail(&mm->roots[i]->tmp_link, &dfs);
> > > -
> > >           do {
> > >                   u64 block_start;
> > >                   u64 block_end;
> > > 
> > > -                block = list_first_entry_or_null(&dfs,
> > > -                                                 struct gpu_buddy_block,
> > > -                                                 tmp_link);
> > > -                if (!block)
> > > +                block = __get_candidate_block(mm, &dfs, &cursor);
> > > +                if (IS_ERR(block))
> > >                           break;
> > > 
> > > -                list_del(&block->tmp_link);
> > > -
> > >                   if (gpu_buddy_block_order(block) < order)
> > >                           continue;
> > > 
> > > @@ -1023,6 +1051,7 @@ static int __alloc_range(struct gpu_buddy *mm,
> > >           LIST_HEAD(allocated);
> > >           u64 end;
> > >           int err;
> > > +        uint32_t cursor = list_empty(dfs) ? 0 : mm->n_roots;
> > > 
> > >           end = start + size - 1;
> > > 
> > > @@ -1030,14 +1059,10 @@ static int __alloc_range(struct gpu_buddy *mm,
> > >                   u64 block_start;
> > >                   u64 block_end;
> > > 
> > > -                block = list_first_entry_or_null(dfs,
> > > -                                                 struct gpu_buddy_block,
> > > -                                                 tmp_link);
> > > -                if (!block)
> > > +                block = __get_candidate_block(mm, dfs, &cursor);
> > > +                if (IS_ERR(block))
> > >                           break;
> > > 
> > > -                list_del(&block->tmp_link);
> > > -
> > >                   block_start = gpu_buddy_block_offset(block);
> > >                   block_end = block_start + gpu_buddy_block_size(mm, block) - 1;
> > > 
> > > @@ -1109,10 +1134,6 @@ static int __gpu_buddy_alloc_range(struct gpu_buddy *mm,
> > >                                      struct list_head *blocks)
> > >   {
> > >           LIST_HEAD(dfs);
> > > -        int i;
> > > -
> > > -        for (i = 0; i < mm->n_roots; ++i)
> > > -                list_add_tail(&mm->roots[i]->tmp_link, &dfs);
> > > 
> > >           return __alloc_range(mm, &dfs, start, size,
> > >                                blocks, total_allocated_on_err);
> > > --
> > > 2.34.1
>

      reply	other threads:[~2026-07-13 13:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09 11:20 [PATCH] gpu: buddy: avoid repeated builds of root dfs when alloc range Zhaoyu Liu
2026-07-13  6:31 ` 刘照玉
2026-07-13  8:02   ` Arunpravin Paneer Selvam
2026-07-13 13:25     ` Zhaoyu Liu [this message]

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=alTnTUq456b3Pf5d@hostpc \
    --to=liuzhaoyu.zackary@picoheart.com \
    --cc=airlied@gmail.com \
    --cc=arunpravin.paneerselvam@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=francois.dugast@intel.com \
    --cc=joelagnelf@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.auld@intel.com \
    --cc=simona@ffwll.ch \
    /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