From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: gpu/buddy: Track per-order free blocks with a scoreboard
Date: Sat, 16 May 2026 14:58:08 +1000 [thread overview]
Message-ID: <review-patch2-20260511164217.150237-3-francois.dugast@intel.com> (raw)
In-Reply-To: <20260511164217.150237-3-francois.dugast@intel.com>
Patch Review
**Assessment: Correct accounting, clean implementation.**
The scoreboard is maintained at all six state-transition points:
| Site | Operation | Correct? |
|------|-----------|----------|
| `mark_free()` | `free_scoreboard[order]++` | Yes — block enters FREE |
| `mark_allocated()` | `free_scoreboard[order]--` | Yes — block leaves FREE |
| `mark_split()` | `free_scoreboard[order]--` | Yes — block leaves FREE |
| `__gpu_buddy_free()` coalesce loop | `free_scoreboard[buddy_order]--` | Yes — buddy removed from tree |
| `__force_merge()` | `free_scoreboard[order]--` | Yes — block removed from tree |
| Four err_undo sites | `free_scoreboard[order]--` | Yes — block removed from tree |
The coalesce loop in `__gpu_buddy_free` only decrements for the buddy (not the block), because the block was already accounted for by the caller (either the err_undo decrement or `mark_free`→`mark_allocated` transition). The final `mark_free(mm, block)` at the bottom of `__gpu_buddy_free` then increments the scoreboard for the coalesced (higher-order) block. This is correct.
**Memory management** is handled properly:
- `gpu_buddy_init()`: `kcalloc` with proper cleanup label `out_free_scoreboard` on the error path
- `gpu_buddy_fini()`: `kfree(mm->free_scoreboard)`
**Minor nit on the header comment:**
```c
+ /*
+ * Per-order free block scoreboard: free_scoreboard[order] holds the
+ * number of blocks of that order currently in the free state.
+ * Incremented in mark_free(), decremented wherever rbtree_remove() is
+ * called on a free block.
+ */
```
This is a good comment for an internal field. But the "decremented wherever rbtree_remove() is called on a free block" formulation is slightly imprecise — it's also decremented in `mark_split()` which does its own `rbtree_remove` internally. The wording is fine in practice though; it captures the invariant well enough.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-16 4:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 16:41 [PATCH v2 0/3] gpu/buddy: Per-order free and used block scoreboards Francois Dugast
2026-05-11 16:41 ` [PATCH v2 1/3] gpu/buddy: Fix use-after-free in split_block() call sites Francois Dugast
2026-05-16 4:58 ` Claude review: " Claude Code Review Bot
2026-05-11 16:41 ` [PATCH v2 2/3] gpu/buddy: Track per-order free blocks with a scoreboard Francois Dugast
2026-05-15 15:50 ` Matthew Auld
2026-05-16 4:58 ` Claude Code Review Bot [this message]
2026-05-11 16:41 ` [PATCH v2 3/3] gpu/buddy: Track per-order used " Francois Dugast
2026-05-16 4:58 ` Claude review: " Claude Code Review Bot
2026-05-16 4:58 ` Claude review: gpu/buddy: Per-order free and used block scoreboards Claude Code Review Bot
-- strict thread matches above, loose matches on Subject: below --
2026-05-04 13:52 [PATCH 0/2] " Francois Dugast
2026-05-04 13:52 ` [PATCH 1/2] gpu/buddy: Track per-order free blocks with a scoreboard Francois Dugast
2026-05-04 22:19 ` Claude review: " Claude Code Review Bot
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=review-patch2-20260511164217.150237-3-francois.dugast@intel.com \
--to=claude-review@example.com \
--cc=dri-devel-reviews@example.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