mm/vmscan: mitigate spurious kswapd_failures reset and add tracepoints
Subsystems (7)
v3 cover mm/vmscan: mitigate spurious kswapd_failures reset and add tracepoints
== Problem ==
We observed an issue in production on a multi-NUMA system where kswapd runs endlessly, causing sustained heavy IO READ pressure across the entire system.
The root cause is that direct reclaim triggered by cgroup memory.high keeps resetting kswapd_failures to 0, even when the node cannot be balanced. This prevents kswapd from ever stopping after reaching MAX_RECLAIM_RETRIES.
```bash
bpftrace -e '
#include <linux/mmzone.h>
#include <linux/shrinker.h>
kprobe:balance_pgdat {
$pgdat = (struct pglist_data *)arg0;
if ($pgdat->kswapd_failures > 0) {
printf("[node %d] [%lu] kswapd end, kswapd_failures %d\n",
$pgdat->node_id, jiffies, $pgdat->kswapd_failures);
}
}
tracepoint:vmscan:mm_vmscan_direct_reclaim_end {
printf("[cpu %d] [%ul] reset kswapd_failures %d \n", cpu, jiffies,
args.nr_reclaimed)
}
'
```The trace results showed that when kswapd_failures reaches 15, continuous direct reclaim keeps resetting it to 0. This was accompanied by a flood of kswapd_failures log entries, and shortly after, we observed massive refaults occurring.
== Solution ==
Patch 1 fixes the issue by only resetting kswapd_failures when the node is actually balanced. This introduces pgdat_try_reset_kswapd_failures() as a wrapper that checks pgdat_balanced() before resetting.
Patch 2 extends the wrapper to track why kswapd_failures was reset, adding tracepoints for better observability:
- mm_vmscan_reset_kswapd_failures: traces each reset with reason
- mm_vmscan_kswapd_reclaim_fail: traces each kswapd reclaim failure
---
v2 -> v3: https://lore.kernel.org/all/[email protected]/
- Add tracepoints for kswapd_failures reset and reclaim failure
- Expand commit message with test results
v1 -> v2: https://lore.kernel.org/all/[email protected]/
Jiayuan Chen (2):
mm/vmscan: mitigate spurious kswapd_failures reset from direct reclaim mm/vmscan: add tracepoint and reason for kswapd_failures reset
include/linux/mmzone.h | 9 +++++++ include/trace/events/vmscan.h | 51 +++++++++++++++++++++++++++++++++++ mm/memory-tiers.c | 2 +- mm/page_alloc.c | 2 +- mm/vmscan.c | 33 ++++++++++++++++++++--- 5 files changed, 91 insertions(+), 6 deletions(-)
Signature · 1 line
2.43.0
PATCH v3 1/2 mm/vmscan: mitigate spurious kswapd_failures reset from direct reclaim
From: Jiayuan Chen <[email protected]>
When kswapd fails to reclaim memory, kswapd_failures is incremented. Once it reaches MAX_RECLAIM_RETRIES, kswapd stops running to avoid futile reclaim attempts. However, any successful direct reclaim unconditionally resets kswapd_failures to 0, which can cause problems.
We observed an issue in production on a multi-NUMA system where a process allocated large amounts of anonymous pages on a single NUMA node, causing its watermark to drop below high and evicting most file pages:
$ numastat -m
Per-node system memory usage (in MBs):
Node 0 Node 1 Total
--------------- --------------- ---------------
MemTotal 128222.19 127983.91 256206.11
MemFree 1414.48 1432.80 2847.29
MemUsed 126807.71 126551.11 252358.82
SwapCached 0.00 0.00 0.00
Active 29017.91 25554.57 54572.48
Inactive 92749.06 95377.00 188126.06
Active(anon) 28998.96 23356.47 52355.43
Inactive(anon) 92685.27 87466.11 180151.39
Active(file) 18.95 2198.10 2217.05
Inactive(file) 63.79 7910.89 7974.68With swap disabled, only file pages can be reclaimed. When kswapd is woken (e.g., via wake_all_kswapds()), it runs continuously but cannot raise free memory above the high watermark since reclaimable file pages are insufficient. Normally, kswapd would eventually stop after kswapd_failures reaches MAX_RECLAIM_RETRIES.
However, containers on this machine have memory.high set in their cgroup. Business processes continuously trigger the high limit, causing frequent direct reclaim that keeps resetting kswapd_failures to 0. This prevents kswapd from ever stopping.
The key insight is that direct reclaim triggered by cgroup memory.high performs aggressive scanning to throttle the allocating process. With sufficiently aggressive scanning, even hot pages will eventually be reclaimed, making direct reclaim "successful" at freeing some memory. However, this success does not mean the node has reached a balanced state - the freed memory may still be insufficient to bring free pages above the high watermark. Unconditionally resetting kswapd_failures in this case keeps kswapd alive indefinitely.
The result is that kswapd runs endlessly. Unlike direct reclaim which only reclaims from the allocating cgroup, kswapd scans the entire node's memory. This causes hot file pages from all workloads on the node to be evicted, not just those from the cgroup triggering memory.high. These pages constantly refault, generating sustained heavy IO READ pressure across the entire system.
Fix this by only resetting kswapd_failures when the node is actually balanced. This allows both kswapd and direct reclaim to clear kswapd_failures upon successful reclaim, but only when the reclaim actually resolves the memory pressure (i.e., the node becomes balanced).
--- mm/vmscan.c | 23 +++++++++++++++++++++-- 1 file changed, 21 insertions(+), 2 deletions(-)
mm/vmscan.c +21 -2
@@ -2650,6 +2650,25 @@ static bool can_age_anon_pages(struct lruvec *lruvec, lruvec_memcg(lruvec)); } +static void pgdat_reset_kswapd_failures (pg_data_t *pgdat) +{ +atomic_set (&pgdat->kswapd_failures,0 ); +} + +/* +* Reset kswapd_failures only when the node is balanced. Without this +* check, successful direct reclaim (e.g., from cgroup memory.high +* throttling) can keep resetting kswapd_failures even when the node +* cannot be balanced, causing kswapd to run endlessly. +*/ +static bool pgdat_balanced (pg_data_t *pgdat,int order,int highest_zoneidx); +static inline void pgdat_try_reset_kswapd_failures (struct pglist_data *pgdat, +struct scan_control *sc) +{ +if (pgdat_balanced (pgdat, sc->order, sc->reclaim_idx)) +pgdat_reset_kswapd_failures (pgdat); +} +#ifdef CONFIG_LRU_GEN #ifdef CONFIG_LRU_GEN_ENABLED
@@ -5067,7 +5086,7 @@ static void lru_gen_shrink_node(struct pglist_data *pgdat, struct scan_control *blk_finish_plug (&plug); done:if (sc->nr_reclaimed > reclaimed) -atomic_set (&pgdat->kswapd_failures,0 ); +pgdat_try_reset_kswapd_failures (pgdat, sc); }/******************************************************************************
@@ -6141,7 +6160,7 @@ static void shrink_node(pg_data_t *pgdat, struct scan_control *sc)* successful direct reclaim run will revive a dormant kswapd. */ if (reclaimable) -atomic_set (&pgdat->kswapd_failures,0 ); +pgdat_try_reset_kswapd_failures (pgdat, sc);else if (sc->cache_trim_mode) sc->cache_trim_mode_failed =1 ; }
Signature · 1 line
2.43.0
Johannes Weiner
maintainerRe: [PATCH v3 1/2] mm/vmscan: mitigate spurious kswapd_failures reset from direct reclaim
Quoted 54 lines · Jiayuan Chen
From: Jiayuan Chen <[email protected]>
When kswapd fails to reclaim memory,
kswapd_failuresis incremented. Once it reachesMAX_RECLAIM_RETRIES, kswapd stops running to avoid futile reclaim attempts. However, any successful direct reclaim unconditionally resetskswapd_failuresto 0, which can cause problems.We observed an issue in production on a multi-NUMA system where a process allocated large amounts of anonymous pages on a single NUMA node, causing its watermark to drop below high and evicting most file pages:
$ numastat -m Per-node system memory usage (in MBs): Node 0 Node 1 Total --------------- --------------- --------------- MemTotal 128222.19 127983.91 256206.11 MemFree 1414.48 1432.80 2847.29 MemUsed 126807.71 126551.11 252358.82 SwapCached 0.00 0.00 0.00 Active 29017.91 25554.57 54572.48 Inactive 92749.06 95377.00 188126.06 Active(anon) 28998.96 23356.47 52355.43 Inactive(anon) 92685.27 87466.11 180151.39 Active(file) 18.95 2198.10 2217.05 Inactive(file) 63.79 7910.89 7974.68With swap disabled, only file pages can be reclaimed. When kswapd is woken (e.g., via
wake_all_kswapds()), it runs continuously but cannot raise free memory above the high watermark since reclaimable file pages are insufficient. Normally, kswapd would eventually stop afterkswapd_failuresreachesMAX_RECLAIM_RETRIES.However, containers on this machine have memory.high set in their cgroup. Business processes continuously trigger the high limit, causing frequent direct reclaim that keeps resetting
kswapd_failuresto 0. This prevents kswapd from ever stopping.The key insight is that direct reclaim triggered by cgroup memory.high performs aggressive scanning to throttle the allocating process. With sufficiently aggressive scanning, even hot pages will eventually be reclaimed, making direct reclaim "successful" at freeing some memory. However, this success does not mean the node has reached a balanced state - the freed memory may still be insufficient to bring free pages above the high watermark. Unconditionally resetting
kswapd_failuresin this case keeps kswapd alive indefinitely.The result is that kswapd runs endlessly. Unlike direct reclaim which only reclaims from the allocating cgroup, kswapd scans the entire node's memory. This causes hot file pages from all workloads on the node to be evicted, not just those from the cgroup triggering memory.high. These pages constantly refault, generating sustained heavy IO READ pressure across the entire system.
Quoted 7 lines
Fix this by only resetting
kswapd_failureswhen the node is actually balanced. This allows both kswapd and direct reclaim to clearkswapd_failuresupon successful reclaim, but only when the reclaim actually resolves the memory pressure (i.e., the node becomes balanced).Signed-off-by Jiayuan Chen <[email protected]>Signed-off-by Jiayuan Chen <[email protected]>
Great analysis, and I agree with both the fix and adding tracepoints.
Two minor nits:
Quoted 5 lines
mm/vmscan.c +1
-0@@ -2650,6 +2650,25 @@ static bool can_age_anon_pages(struct lruvec *lruvec, lruvec_memcg(lruvec)); } +static void pgdat_reset_kswapd_failures (pg_data_t *pgdat)
mm/vmscan.c static bool can_age_anon_pages(struct lruvec *lruvec, · line 2663
Quoted 10 lines
mm/vmscan.c +10
-0+{ +atomic_set (&pgdat->kswapd_failures,0 ); +/* +* Reset kswapd_failures only when the node is balanced. Without this +* check, successful direct reclaim (e.g., from cgroup memory.high +* throttling) can keep resetting kswapd_failures even when the node +* cannot be balanced, causing kswapd to run endlessly. +*/ +static bool pgdat_balanced (pg_data_t *pgdat,int order,int highest_zoneidx); +static inline void pgdat_try_reset_kswapd_failures(struct pglist_data *pgdat,
Please remove the inline, the compiler will figure it out.
mm/vmscan.c static bool can_age_anon_pages(struct lruvec *lruvec, · line 2670
Quoted 5 lines
mm/vmscan.c +5
-0+ struct scan_control *sc) +{ +if (pgdat_balanced (pgdat, sc->order, sc->reclaim_idx)) +pgdat_reset_kswapd_failures (pgdat); +}
As this is kswapd API, please move these down to after wakeup_kswapd().
I think we can streamline the names a bit. We already use "hopeless" for that state in the comments; can you please rename the functions kswapd_clear_hopeless() and kswapd_try_clear_hopeless()?
We should then also replace the open-coded kswapd_failure checks with kswapd_test_hopeless(). But I can send a follow-up patch if you don't want to, just let me know.
Re: [PATCH v3 1/2] mm/vmscan: mitigate spurious kswapd_failures reset from direct reclaim
2026/1/17 01:00, "Johannes Weiner" <[email protected] mailto:[email protected]?to=%22Johannes%20Weiner%22%20%3Channes%40cmpxchg.org%3E > wrote:
[...]
Quoted 33 lines
Quoted 1 line
Great analysis, and I agree with both the fix and adding tracepoints.
Two minor nits:
Quoted 7 lines
(quoted diff) +0
-0@@ -2650,6 +2650,25 @@ static bool can_age_anon_pages(struct lruvec *lruvec, lruvec_memcg(lruvec)); } +static void pgdat_reset_kswapd_failures(pg_data_t *pgdat)Review static bool can_age_anon_pages(struct lruvec *lruvec,
Quoted 10 lines
(quoted diff) +0
-0+{ + atomic_set(&pgdat->kswapd_failures, 0); +/* + * Reset kswapd_failures only when the node is balanced. Without this + * check, successful direct reclaim (e.g., from cgroup memory.high + * throttling) can keep resetting kswapd_failures even when the node + * cannot be balanced, causing kswapd to run endlessly. + */ +static bool pgdat_balanced(pg_data_t *pgdat, int order, int highest_zoneidx); +static inline void pgdat_try_reset_kswapd_failures(struct pglist_data *pgdat,Please remove the inline, the compiler will figure it out.
Quoted 7 lines
+ struct
scan_control*sc)
+{
+ if (pgdat_balanced(pgdat, sc->order, sc->reclaim_idx))
+pgdat_reset_kswapd_failures(pgdat);
+}As this is kswapd API, please move these down to after
wakeup_kswapd().
Quoted 8 lines
I think we can streamline the names a bit. We already use "hopeless" for that state in the comments; can you please rename the functions
kswapd_clear_hopeless()andkswapd_try_clear_hopeless()?We should then also replace the open-coded
kswapd_failurechecks withkswapd_test_hopeless(). But I can send a follow-up patch if you don't want to, just let me know.
Thanks, Johannes and Shakeel. I'll send an updated version with these fixes.
Re: [PATCH v3 1/2] mm/vmscan: mitigate spurious kswapd_failures reset from direct reclaim
In reply to Jiayuan ChenQuoted 54 lines · Jiayuan Chen
From: Jiayuan Chen <[email protected]>
When kswapd fails to reclaim memory,
kswapd_failuresis incremented. Once it reachesMAX_RECLAIM_RETRIES, kswapd stops running to avoid futile reclaim attempts. However, any successful direct reclaim unconditionally resetskswapd_failuresto 0, which can cause problems.We observed an issue in production on a multi-NUMA system where a process allocated large amounts of anonymous pages on a single NUMA node, causing its watermark to drop below high and evicting most file pages:
$ numastat -m Per-node system memory usage (in MBs): Node 0 Node 1 Total --------------- --------------- --------------- MemTotal 128222.19 127983.91 256206.11 MemFree 1414.48 1432.80 2847.29 MemUsed 126807.71 126551.11 252358.82 SwapCached 0.00 0.00 0.00 Active 29017.91 25554.57 54572.48 Inactive 92749.06 95377.00 188126.06 Active(anon) 28998.96 23356.47 52355.43 Inactive(anon) 92685.27 87466.11 180151.39 Active(file) 18.95 2198.10 2217.05 Inactive(file) 63.79 7910.89 7974.68With swap disabled, only file pages can be reclaimed. When kswapd is woken (e.g., via
wake_all_kswapds()), it runs continuously but cannot raise free memory above the high watermark since reclaimable file pages are insufficient. Normally, kswapd would eventually stop afterkswapd_failuresreachesMAX_RECLAIM_RETRIES.However, containers on this machine have memory.high set in their cgroup. Business processes continuously trigger the high limit, causing frequent direct reclaim that keeps resetting
kswapd_failuresto 0. This prevents kswapd from ever stopping.The key insight is that direct reclaim triggered by cgroup memory.high performs aggressive scanning to throttle the allocating process. With sufficiently aggressive scanning, even hot pages will eventually be reclaimed, making direct reclaim "successful" at freeing some memory. However, this success does not mean the node has reached a balanced state - the freed memory may still be insufficient to bring free pages above the high watermark. Unconditionally resetting
kswapd_failuresin this case keeps kswapd alive indefinitely.The result is that kswapd runs endlessly. Unlike direct reclaim which only reclaims from the allocating cgroup, kswapd scans the entire node's memory. This causes hot file pages from all workloads on the node to be evicted, not just those from the cgroup triggering memory.high. These pages constantly refault, generating sustained heavy IO READ pressure across the entire system.
Quoted 7 lines
Fix this by only resetting
kswapd_failureswhen the node is actually balanced. This allows both kswapd and direct reclaim to clearkswapd_failuresupon successful reclaim, but only when the reclaim actually resolves the memory pressure (i.e., the node becomes balanced).Signed-off-by Jiayuan Chen <[email protected]>Signed-off-by Jiayuan Chen <[email protected]>
After incorporating suggestions from Johannes, you can add:
PATCH v3 2/2 mm/vmscan: add tracepoint and reason for kswapd_failures reset
In reply to Jiayuan ChenFrom: Jiayuan Chen <[email protected]>
Currently, kswapd_failures is reset in multiple places (kswapd, direct reclaim, PCP freeing, memory-tiers), but there's no way to trace when and why it was reset, making it difficult to debug memory reclaim issues.
This patch:
1. Introduce pgdat_reset_kswapd_failures() as a wrapper function to centralize kswapd_failures reset logic.
2. Add reset_kswapd_failures_reason enum to distinguish reset sources:
- RESET_KSWAPD_FAILURES_KSWAPD: reset from kswapd context
- RESET_KSWAPD_FAILURES_DIRECT: reset from direct reclaim
- RESET_KSWAPD_FAILURES_PCP: reset from PCP page freeing
- RESET_KSWAPD_FAILURES_OTHER: reset from other paths
3. Add tracepoints for better observability:
- mm_vmscan_reset_kswapd_failures: traces each reset with reason
- mm_vmscan_kswapd_reclaim_fail: traces each kswapd reclaim failure
---
Test results:
$ trace-cmd record -e vmscan:mm_vmscan_reset_kswapd_failures -e vmscan:mm_vmscan_kswapd_reclaim_fail $ # generate memory pressure $ trace-cmd report cpus=4 kswapd1-73 [002] 24.863112: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=1 kswapd1-73 [002] 24.863472: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=2 kswapd1-73 [002] 24.863813: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=3 kswapd1-73 [002] 24.864141: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=4 kswapd1-73 [002] 24.864462: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=5 kswapd1-73 [002] 24.864779: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=6 kswapd1-73 [002] 24.865103: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=7 kswapd1-73 [002] 24.865421: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=8 kswapd1-73 [002] 24.865737: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=9 kswapd1-73 [002] 24.866070: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=10 kswapd1-73 [002] 24.866385: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=11 kswapd1-73 [002] 24.866701: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=12 kswapd1-73 [002] 24.867016: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=13 kswapd1-73 [002] 24.867333: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=14 kswapd1-73 [002] 24.867649: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=15 kswapd1-73 [002] 24.867965: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=16 kswapd0-72 [001] 25.020464: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=1 kswapd0-72 [001] 25.021054: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=2 kswapd0-72 [001] 25.021628: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=3 kswapd0-72 [001] 25.022217: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=4 kswapd0-72 [001] 25.022790: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=5 kswapd0-72 [001] 25.023366: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=6 kswapd0-72 [001] 25.023937: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=7 kswapd0-72 [001] 25.024511: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=8 kswapd0-72 [001] 25.025092: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=9 kswapd0-72 [001] 25.025665: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=10 kswapd0-72 [001] 25.026249: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=11 kswapd0-72 [001] 25.026824: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=12 kswapd0-72 [001] 25.027398: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=13 kswapd0-72 [001] 25.027976: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=14 kswapd0-72 [001] 25.028554: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=15 kswapd0-72 [001] 25.029140: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=16 ann-416 [002] 25.577925: mm_vmscan_reset_kswapd_failures: nid=0 reason=PCP dd-417 [002] 35.111721: mm_vmscan_reset_kswapd_failures: nid=1 reason=DIRECT
--- include/linux/mmzone.h | 9 +++++++ include/trace/events/vmscan.h | 51 +++++++++++++++++++++++++++++++++++ mm/memory-tiers.c | 2 +- mm/page_alloc.c | 2 +- mm/vmscan.c | 16 +++++++---- 5 files changed, 73 insertions(+), 7 deletions(-)
include/linux/mmzone.h +9 -0
@@ -1531,6 +1531,15 @@ static inline unsigned long pgdat_end_pfn(pg_data_t *pgdat)return pgdat->node_start_pfn + pgdat->node_spanned_pages; } +enum reset_kswapd_failures_reason { +RESET_KSWAPD_FAILURES_OTHER =0 , +RESET_KSWAPD_FAILURES_KSWAPD , +RESET_KSWAPD_FAILURES_DIRECT , +RESET_KSWAPD_FAILURES_PCP , +}; + +void pgdat_reset_kswapd_failures (pg_data_t *pgdat,enum reset_kswapd_failures_reason reason); +#include <linux/memory_hotplug.h> void build_all_zonelists (pg_data_t *pgdat);
include/trace/events/vmscan.h +51 -0
63 lines not on this page · raw message
mm/memory-tiers.c +1 -1
@@ -956,7 +956,7 @@ static ssize_t demotion_enabled_store(struct kobject *kobj,struct pglist_data *pgdat;for_each_online_pgdat (pgdat) -atomic_set (&pgdat->kswapd_failures,0 ); +pgdat_reset_kswapd_failures (pgdat,RESET_KSWAPD_FAILURES_OTHER ); }return count;
mm/page_alloc.c +1 -1
@@ -2918,7 +2918,7 @@ static bool free_frozen_page_commit(struct zone *zone,*/ if (atomic_read (&pgdat->kswapd_failures) >=MAX_RECLAIM_RETRIES &&next_memory_node (pgdat->node_id) <MAX_NUMNODES ) -atomic_set (&pgdat->kswapd_failures,0 ); +pgdat_reset_kswapd_failures (pgdat,RESET_KSWAPD_FAILURES_PCP ); }return ret; }
mm/vmscan.c +11 -5
@@ -2650,9 +2650,11 @@ static bool can_age_anon_pages(struct lruvec *lruvec, lruvec_memcg(lruvec)); } -static void pgdat_reset_kswapd_failures (pg_data_t *pgdat) +void pgdat_reset_kswapd_failures (pg_data_t *pgdat,enum reset_kswapd_failures_reason reason) { -atomic_set (&pgdat->kswapd_failures,0 ); +/* Only trace actual resets, not redundant zero-to-zero */ +if (atomic_xchg (&pgdat->kswapd_failures,0 )) +trace_mm_vmscan_reset_kswapd_failures (pgdat->node_id, reason); }/*
@@ -2666,7 +2668,8 @@ static inline void pgdat_try_reset_kswapd_failures(struct pglist_data *pgdat, struct scan_control *sc) {if (pgdat_balanced (pgdat, sc->order, sc->reclaim_idx)) -pgdat_reset_kswapd_failures (pgdat); +pgdat_reset_kswapd_failures (pgdat,current_is_kswapd () ? +RESET_KSWAPD_FAILURES_KSWAPD :RESET_KSWAPD_FAILURES_DIRECT ); }#ifdef CONFIG_LRU_GEN
@@ -7153,8 +7156,11 @@ static int balance_pgdat(pg_data_t *pgdat, int order, int highest_zoneidx)* watermark_high at this point. We need to avoid increasing the * failure count to prevent the kswapd thread from stopping. */ -if (!sc.nr_reclaimed && !boosted) -atomic_inc (&pgdat->kswapd_failures); +if (!sc.nr_reclaimed && !boosted) { +int fail_cnt =atomic_inc_return (&pgdat->kswapd_failures); +/* kswapd context, low overhead to trace every failure */ +trace_mm_vmscan_kswapd_reclaim_fail (pgdat->node_id, fail_cnt); + } out:clear_reclaim_active (pgdat, highest_zoneidx);
Signature · 1 line
2.43.0
Re: [PATCH v3 2/2] mm/vmscan: add tracepoint and reason for kswapd_failures reset
Quoted 64 lines · Jiayuan Chen
From: Jiayuan Chen <[email protected]>
Currently,
kswapd_failuresis reset in multiple places (kswapd, direct reclaim, PCP freeing, memory-tiers), but there's no way to trace when and why it was reset, making it difficult to debug memory reclaim issues.This patch:
1. Introduce
pgdat_reset_kswapd_failures()as a wrapper function to centralizekswapd_failuresreset logic.2. Add
reset_kswapd_failures_reasonenum to distinguish reset sources:
-RESET_KSWAPD_FAILURES_KSWAPD: reset from kswapd context
-RESET_KSWAPD_FAILURES_DIRECT: reset from direct reclaim
-RESET_KSWAPD_FAILURES_PCP: reset from PCP page freeing
-RESET_KSWAPD_FAILURES_OTHER: reset from other paths3. Add tracepoints for better observability:
-mm_vmscan_reset_kswapd_failures: traces each reset with reason
-mm_vmscan_kswapd_reclaim_fail: traces each kswapd reclaim failure---
Test results:$ trace-cmd record -e vmscan:mm_vmscan_reset_kswapd_failures -e vmscan:mm_vmscan_kswapd_reclaim_fail $ # generate memory pressure $ trace-cmd report cpus=4 kswapd1-73 [002] 24.863112: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=1 kswapd1-73 [002] 24.863472: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=2 kswapd1-73 [002] 24.863813: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=3 kswapd1-73 [002] 24.864141: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=4 kswapd1-73 [002] 24.864462: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=5 kswapd1-73 [002] 24.864779: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=6 kswapd1-73 [002] 24.865103: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=7 kswapd1-73 [002] 24.865421: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=8 kswapd1-73 [002] 24.865737: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=9 kswapd1-73 [002] 24.866070: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=10 kswapd1-73 [002] 24.866385: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=11 kswapd1-73 [002] 24.866701: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=12 kswapd1-73 [002] 24.867016: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=13 kswapd1-73 [002] 24.867333: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=14 kswapd1-73 [002] 24.867649: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=15 kswapd1-73 [002] 24.867965: mm_vmscan_kswapd_reclaim_fail: nid=1 failures=16 kswapd0-72 [001] 25.020464: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=1 kswapd0-72 [001] 25.021054: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=2 kswapd0-72 [001] 25.021628: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=3 kswapd0-72 [001] 25.022217: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=4 kswapd0-72 [001] 25.022790: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=5 kswapd0-72 [001] 25.023366: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=6 kswapd0-72 [001] 25.023937: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=7 kswapd0-72 [001] 25.024511: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=8 kswapd0-72 [001] 25.025092: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=9 kswapd0-72 [001] 25.025665: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=10 kswapd0-72 [001] 25.026249: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=11 kswapd0-72 [001] 25.026824: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=12 kswapd0-72 [001] 25.027398: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=13 kswapd0-72 [001] 25.027976: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=14 kswapd0-72 [001] 25.028554: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=15 kswapd0-72 [001] 25.029140: mm_vmscan_kswapd_reclaim_fail: nid=0 failures=16 ann-416 [002] 25.577925: mm_vmscan_reset_kswapd_failures: nid=0 reason=PCP dd-417 [002] 35.111721: mm_vmscan_reset_kswapd_failures: nid=1 reason=DIRECT
Quoted 2 lines
Signed-off-by Jiayuan Chen <[email protected]>Signed-off-by Jiayuan Chen <[email protected]>
Thanks for adding this.
Andrew Morton
maintainerQuoted 10 lines · On Wed, 14 Jan 2026 15:40:34 +0800 Jiayuan Chen <[email protected]> wrote:
== Problem ==
We observed an issue in production on a multi-NUMA system where kswapd runs endlessly, causing sustained heavy IO READ pressure across the entire system.
== Solution ==
...
Thanks, I'll update mm.git to this version to keep the series under test while Michal and Shakeel continue their review (please!).