* [PATCH 0/1] mm/page_alloc: dynamic min_free_kbytes adjustment
@ 2026-01-04 12:17 wujing
0 siblings, 0 replies; 2+ messages in thread
From: wujing @ 2026-01-04 12:17 UTC (permalink / raw)
To: Andrew Morton, Vlastimil Babka
Cc: Suren Baghdasaryan, Michal Hocko, Brendan Jackman,
Johannes Weiner, Zi Yan, linux-mm, linux-kernel, Qiliang Yuan,
wujing
Atomic allocations (GFP_ATOMIC), particularly in network interrupt contexts,
are prone to failure during bursts of traffic if the pre-configured
min_free_kbytes (atomic reserve) is insufficient. These failures lead to
packet drops and performance degradation.
Static tuning of vm.min_free_kbytes is often challenging: setting it too
low risks drops, while setting it too high wastes valuable memory.
This patch series introduces a reactive mechanism that:
1. Detects critical order-0 GFP_ATOMIC allocation failures.
2. Automatically doubles vm.min_free_kbytes to reserve more memory for
future bursts.
3. Enforces a safety cap (1% of total RAM) to prevent OOM or excessive waste.
This allows the system to self-adjust to the workload's specific atomic
memory requirements without manual intervention.
wujing (1):
mm/page_alloc: auto-tune min_free_kbytes on atomic allocation failure
mm/page_alloc.c | 33 +++++++++++++++++++++++++++++++++
1 file changed, 33 insertions(+)
--
2.39.5
^ permalink raw reply [flat|nested] 2+ messages in thread
* [PATCH 0/1] mm/page_alloc: dynamic min_free_kbytes adjustment
@ 2026-01-04 12:23 wujing
0 siblings, 0 replies; 2+ messages in thread
From: wujing @ 2026-01-04 12:23 UTC (permalink / raw)
To: Andrew Morton, Vlastimil Babka
Cc: Suren Baghdasaryan, Michal Hocko, Brendan Jackman,
Johannes Weiner, Zi Yan, linux-mm, linux-kernel, Qiliang Yuan,
wujing
Atomic allocations (GFP_ATOMIC), particularly in network interrupt contexts,
are prone to failure during bursts of traffic if the pre-configured
min_free_kbytes (atomic reserve) is insufficient. These failures lead to
packet drops and performance degradation.
Static tuning of vm.min_free_kbytes is often challenging: setting it too
low risks drops, while setting it too high wastes valuable memory.
This patch series introduces a reactive mechanism that:
1. Detects critical order-0 GFP_ATOMIC allocation failures.
2. Automatically doubles vm.min_free_kbytes to reserve more memory for
future bursts.
3. Enforces a safety cap (1% of total RAM) to prevent OOM or excessive waste.
This allows the system to self-adjust to the workload's specific atomic
memory requirements without manual intervention.
wujing (1):
mm/page_alloc: auto-tune min_free_kbytes on atomic allocation failure
mm/page_alloc.c | 33 +++++++++++++++++++++++++++++++++
1 file changed, 33 insertions(+)
--
2.39.5
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-01-04 12:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-01-04 12:17 [PATCH 0/1] mm/page_alloc: dynamic min_free_kbytes adjustment wujing
2026-01-04 12:23 wujing
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox