From: Andrew Morton <akpm@linux-foundation.org>
To: Benjamin Lee McQueen <mcq@disroot.org>
Cc: david@kernel.org, lorenzo.stoakes@oracle.com,
Liam.Howlett@oracle.com, vbabka@kernel.org, rppt@kernel.org,
surenb@google.com, mhocko@suse.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/vmpressure: scale window size based on machine memory and CPU count
Date: Fri, 27 Feb 2026 12:28:57 -0800 [thread overview]
Message-ID: <20260227122857.dca67a5f281e39a3e78acc74@linux-foundation.org> (raw)
In-Reply-To: <20260227163333.6394-1-mcq@disroot.org>
On Fri, 27 Feb 2026 10:33:33 -0600 Benjamin Lee McQueen <mcq@disroot.org> wrote:
> the vmpressure window size was recently fixed at 512 pages regardless
> of machine size, this patch makes it scale based on the machine memory
> and CPU count.
Why? Presumably the current code is causing some problem - please
fully describe that.
> --- 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);
Whitespace is odd.
next prev parent reply other threads:[~2026-02-27 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 16:33 Benjamin Lee McQueen
2026-02-27 20:28 ` Andrew Morton [this message]
2026-02-27 22:18 ` Benjamin Lee McQueen
2026-02-27 22:24 ` [PATCH v2] " Benjamin Lee McQueen
2026-02-27 22:15 [PATCH] " Benjamin Lee McQueen
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=20260227122857.dca67a5f281e39a3e78acc74@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mcq@disroot.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
/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