From: Joel Fernandes <joelagnelf@nvidia.com>
To: Sanjay Kumar Yadav <sanjay.kumar.yadav@intel.com>
Cc: dri-devel@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
Matthew Auld <matthew.auld@intel.com>,
Arun Pravin <arunpravin.paneerselvam@amd.com>
Subject: Re: [PATCH v4 1/1] gpu/buddy: Prune exhausted subtrees in range-biased allocation
Date: Sat, 07 Nov 2026 09:56:26 -0500 [thread overview]
Message-ID: <20261107-joel-rb-tb-buddy-prune@nvidia.com> (raw)
In-Reply-To: <20261102051633.2035348-4-sanjay.kumar.yadav@intel.com>
On Mon, Nov 02, 2026 at 10:46:35AM +0530, Sanjay Yadav wrote:
> [...]
> Cc: Matthew Auld <matthew.auld@intel.com>
> Cc: Arun Pravin <arunpravin.paneerselvam@amd.com>
> Cc: Joel Fernandes <joelagnelf@nvidia.com>
> Assisted-by: LLM
> Signed-off-by: Sanjay Yadav <sanjay.kumar.yadav@intel.com>
Reviewed-by: Joel Fernandes <joelagnelf@nvidia.com>
Tested-by: Joel Fernandes <joelagnelf@nvidia.com>
> ---
> drivers/gpu/buddy.c | 56 +++++++++++++++++++++++++++------------
> include/linux/gpu_buddy.h | 7 +++++
> 2 files changed, 46 insertions(+), 17 deletions(-)
next prev parent reply other threads:[~2026-11-07 14:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 5:16 [PATCH v4 0/1] gpu/buddy: Fix quadratic cost of range-biased allocation Sanjay Yadav
2026-11-02 5:16 ` [PATCH v4 1/1] gpu/buddy: Prune exhausted subtrees in " Sanjay Yadav
2026-11-04 12:12 ` Yadav, Sanjay Kumar
2026-11-06 12:20 ` Yadav, Sanjay Kumar
2026-11-06 13:45 ` Joel Fernandes
2026-11-06 15:58 ` Yadav, Sanjay Kumar
2026-11-07 14:56 ` Joel Fernandes [this message]
2026-11-09 6:40 ` Arunpravin Paneer Selvam
2026-11-09 14:07 ` Palacek, William
2026-11-12 14:45 ` Arunpravin Paneer Selvam
2026-11-15 15:53 ` Yadav, Sanjay Kumar
2026-11-02 5:30 ` ✗ CI.checkpatch: warning for gpu/buddy: Fix quadratic cost of range-biased allocation (rev5) Patchwork
2026-11-02 5:33 ` ✓ CI.KUnit: success " Patchwork
2026-11-02 6:06 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-11-02 6:34 ` ✗ Xe.CI.FULL: " 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=20261107-joel-rb-tb-buddy-prune@nvidia.com \
--to=joelagnelf@nvidia.com \
--cc=arunpravin.paneerselvam@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=sanjay.kumar.yadav@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.