[PATCH] mm/vmpressure: scale window size based on machine memory and CPU count

Benjamin Lee McQueen
2026-02-27T22:16:15Z

on systems of different sizes, the fixed 512 page window may not
be suitable and cause excessive false positive memory pressure
notifications.

or should window size be capped to avoid excessive notification
delays on very large systems?

v2: better commit msg, also tried to fix the whitespace.

Signed-off-by: Benjamin Lee McQueen <mcq@disroot.org>
---
mm/vmpressure.c | 16 +++++++++++++---
1 file changed, 13 insertions(+), 3 deletions(-)

diff --git a/mm/vmpressure.c b/mm/vmpressure.c
index 3fbb86996c4d..925659f28dcb 100644
--- a/mm/vmpressure.c
+++ b/mm/vmpressure.c
@@ -32,10 +32,20 @@
* As the vmscan reclaimer logic works with chunks which are multiple of
* SWAP_CLUSTER_MAX, it makes sense to use it for the window size as well.
*
- * TODO: Make the window size depend on machine size, as we do for vmstat
- * thresholds. Currently we set it to 512 pages (2MB for 4KB pages).
+ * Window size is now scaled based on RAM and CPU size, similarly to how
+ * vmstat checks them.
*/
-static const unsigned long vmpressure_win = SWAP_CLUSTER_MAX * 16;
+static unsigned long vmpressure_win;
+
+static int __init vmpressure_win_init(void)
+{
+ unsigned long mem = totalram_pages() >> (27 - PAGE_SHIFT);
+
+ vmpressure_win = SWAP_CLUSTER_MAX * max(16UL,
+ 2UL * fls(num_online_cpus()) * (1 + fls(mem)));
+ return 0;
+}
+core_initcall(vmpressure_win_init);

/*
* These thresholds are used when we account memory pressure through
--
2.51.0