From: Michal Hocko <mhocko@suse.com>
To: Benjamin Lee McQueen <mcq@disroot.org>
Cc: akpm@linux-foundation.org, david@kernel.org,
lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
vbabka@kernel.org, rppt@kernel.org, surenb@google.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: Mon, 2 Mar 2026 09:56:38 +0100 [thread overview]
Message-ID: <aaVQxnNFcbxKYRaX@tiehlicka> (raw)
In-Reply-To: <20260227221555.29969-1-mcq@disroot.org>
On Fri 27-02-26 16:15:55, Benjamin Lee McQueen wrote:
> on systems of different sizes, the fixed 512 page window may not
> be suitable and cause excessive false positive memory pressure
> notifications.
Please be more specific about the issue you are trying to have fixed.
The above is way too generic. How much memory the system has, what do
you consider false positive and why. What is the workload. Etc...
> 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.
Also please refrain from sending new versions in a quick succession
and wait for more feedback to come.
Last but not lease if this is a more of an idea rather than something
aimed to be merged make the fact explicit by RFC prefix to PATCH.
There is much more you can read about the process in Documentation/process/
Thanks
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2026-03-02 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 22:15 Benjamin Lee McQueen
2026-03-02 8:56 ` Michal Hocko [this message]
2026-03-02 12:15 ` Lorenzo Stoakes
-- strict thread matches above, loose matches on Subject: below --
2026-02-27 16:33 Benjamin Lee McQueen
2026-02-27 20:28 ` Andrew Morton
2026-02-27 22:18 ` 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=aaVQxnNFcbxKYRaX@tiehlicka \
--to=mhocko@suse.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--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=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