From: SJ Park <sj@kernel.org>
To: pratmal@google.com
Cc: SJ Park <sj@kernel.org>,
akpm@linux-foundation.org, vbabka@kernel.org, david@kernel.org,
corbet@lwn.net, ljs@kernel.org, skhan@linuxfoundation.org,
anshuman.khandual@arm.com, gthelen@google.com, surenb@google.com,
mhocko@suse.com, jackmanb@google.com, hannes@cmpxchg.org,
ziy@nvidia.com, liam@infradead.org, rppt@kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org,
Brendan Jackman <brendan.jackman@linux.dev>
Subject: Re: [PATCH v4] mm/page_reporting: Add page_reporting_delay_ms module parameter
Date: Fri, 31 Jul 2026 17:02:53 -0700 [thread overview]
Message-ID: <20260801000254.77032-1-sj@kernel.org> (raw)
In-Reply-To: <20260731193705.2902728-1-pratmal@google.com>
Brendan changed his mail address [1]. I added him to the recipient list.
On Fri, 31 Jul 2026 19:37:05 +0000 pratmal@google.com wrote:
> From: Pratyush Mallick <pratmal@google.com>
>
> Free page reporting currently hardcodes a 2-second interval between
> reports. This rigid delay cannot accommodate diverse guest workloads.
>
> This patch introduces a module parameter, page_reporting_delay_ms
> (default: 2000), allowing users to tune the reporting rate:
> - Lower values enable aggressive memory reclamation by returning unused
> pages to the host immediately.
> - Higher values help batch pages during spiky allocation/free churn,
> reducing hypercalls and nested page fault overheads.
>
> Setting the delay to 0 is safe and execution is strictly gated by:
> - reporting is only triggered by high-order page frees.
> - expensive hypercalls are bounded by a slot capacity watermark check
> before proceeding.
Looks good and making sense to me.
>
> Signed-off-by: Pratyush Mallick <pratmal@google.com>
Reviewed-by: SJ Park <sj@kernel.org>
[1] https://lore.kernel.org/20260729-email-change-v1-1-666ae7c2b7fc@google.com
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-08-01 0:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 19:37 [PATCH v4] mm/page_reporting: Add page_reporting_delay_ms module parameter pratmal
2026-07-31 21:34 ` Andrew Morton
2026-07-31 21:41 ` Pratyush Mallick
2026-08-01 0:02 ` SJ Park [this message]
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=20260801000254.77032-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=brendan.jackman@linux.dev \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=gthelen@google.com \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=pratmal@google.com \
--cc=rppt@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=ziy@nvidia.com \
/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