From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/ttm: Introduce ttm_bo_shrink_kswap_maybe_fragmented()
Date: Tue, 05 May 2026 10:00:01 +1000 [thread overview]
Message-ID: <review-patch4-20260430191809.2142544-5-matthew.brost@intel.com> (raw)
In-Reply-To: <20260430191809.2142544-5-matthew.brost@intel.com>
Patch Review
**Subject:** `[PATCH v4 4/6] drm/ttm: Introduce ttm_bo_shrink_kswap_maybe_fragmented()`
Adds a helper in `ttm_bo_util.c`:
```c
+bool ttm_bo_shrink_kswap_maybe_fragmented(int nid, s8 order)
+{
+ if (!order)
+ return false;
+
+ if (!current_is_kswapd())
+ return false;
+
+ if (!numa_valid_node(nid))
+ return false;
+
+#if IS_ENABLED(CONFIG_ZONE_DMA32)
+ zone_type = ZONE_DMA32;
+#else
+ zone_type = ZONE_NORMAL;
+#endif
+
+ for (; zone_type <= ZONE_NORMAL; ++zone_type) {
+ struct zone *zone = &NODE_DATA(nid)->node_zones[zone_type];
+ if (zone_maybe_fragmented_in_shrinker(zone))
+ return true;
+ }
+ return false;
+}
```
**Concerns:**
1. **The zone iteration logic is confusing.** When `CONFIG_ZONE_DMA32` is enabled, it iterates from `ZONE_DMA32` to `ZONE_NORMAL`. When it's disabled, it only checks `ZONE_NORMAL` (since `zone_type = ZONE_NORMAL` and the loop condition is `<= ZONE_NORMAL`). This is correct but the `#if`/`#else` makes it harder to read than necessary. A comment explaining the iteration range would help.
2. **`ZONE_DMA` is excluded.** The helper only checks DMA32 and NORMAL zones. This is probably intentional (GPU memory typically comes from these zones) but isn't documented.
3. **Return semantics are good.** The early returns for `!order` (order-0 allocations shouldn't trigger fragmentation avoidance), `!current_is_kswapd()` (only affects background reclaim), and `!numa_valid_node(nid)` are sensible guards.
4. **Docstring typo:** "false is not" should be "false if not".
```c
* Return: true if in kswap and memory appears fragmented, false is not.
```
5. **The `order` parameter is `s8` but only tested for non-zero.** The actual order value isn't used beyond the zero check. If the intent is only "was this a higher-order allocation?", a bool would be clearer. However, passing `order` through is forward-compatible for future refinements that may want the actual value.
**Minor issues only. Functionally sound.**
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-05 0:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 19:18 [PATCH v4 0/6] mm, drm/ttm, drm/xe: Avoid reclaim/eviction loops under fragmentation Matthew Brost
2026-04-30 19:18 ` [PATCH v4 1/6] mm: Wire up order in shrink_control Matthew Brost
2026-05-05 0:00 ` Claude review: " Claude Code Review Bot
2026-04-30 19:18 ` [PATCH v4 2/6] mm: Introduce zone_maybe_fragmented_in_shrinker() Matthew Brost
2026-05-01 0:50 ` Santa, Carlos
[not found] ` <f25f27a1-bf09-44bd-9b37-49f159d82d6a@panix.com>
2026-05-01 20:00 ` PATCH v4 0/6] mm, drm/ttm, drm/xe: Avoid reclaim/eviction loops under fragmentation Matthew Brost
[not found] ` <1bc0b1a7-a01f-4dc2-ad7a-3a05f975331e@panix.com>
2026-05-01 21:10 ` Matthew Brost
2026-05-01 22:33 ` Matthew Brost
2026-05-05 0:00 ` Claude review: mm: Introduce zone_maybe_fragmented_in_shrinker() Claude Code Review Bot
2026-04-30 19:18 ` [PATCH v4 3/6] drm/ttm: Issue direct reclaim at beneficial_order Matthew Brost
2026-05-04 7:16 ` Christian König
2026-05-05 0:00 ` Claude review: " Claude Code Review Bot
2026-04-30 19:18 ` [PATCH v4 4/6] drm/ttm: Introduce ttm_bo_shrink_kswap_maybe_fragmented() Matthew Brost
2026-05-05 0:00 ` Claude Code Review Bot [this message]
2026-04-30 19:18 ` [PATCH v4 5/6] drm/xe: Set TTM device beneficial_order to 9 (2M) Matthew Brost
2026-05-05 0:00 ` Claude review: " Claude Code Review Bot
2026-04-30 19:18 ` [PATCH v4 6/6] drm/xe: Avoid shrinker reclaim from kswapd under fragmentation Matthew Brost
2026-05-05 0:00 ` Claude review: " Claude Code Review Bot
2026-04-30 23:01 ` [PATCH v4 0/6] mm, drm/ttm, drm/xe: Avoid reclaim/eviction loops " Andrew Morton
2026-05-01 6:28 ` Matthew Brost
2026-05-01 12:51 ` Andrew Morton
2026-05-01 1:42 ` Dave Chinner
2026-05-01 7:09 ` Matthew Brost
2026-05-05 0:00 ` Claude review: " Claude Code Review Bot
-- strict thread matches above, loose matches on Subject: below --
2026-04-30 18:23 [PATCH v3 0/6] " Matthew Brost
2026-04-30 18:23 ` [PATCH v3 4/6] drm/ttm: Introduce ttm_bo_shrink_kswap_maybe_fragmented() Matthew Brost
2026-05-05 0:13 ` 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-patch4-20260430191809.2142544-5-matthew.brost@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