* [PATCH v3] mm/page_reporting: Add page_reporting_delay_ms module parameter
@ 2026-07-27 23:05 pratmal
2026-07-27 23:59 ` SJ Park
2026-07-28 1:13 ` Andrew Morton
0 siblings, 2 replies; 3+ messages in thread
From: pratmal @ 2026-07-27 23:05 UTC (permalink / raw)
To: akpm, vbabka, david, sj, corbet
Cc: skhan, anshuman.khandual, gthelen, surenb, mhocko, jackmanb,
hannes, ziy, ljs, liam, rppt, linux-mm, linux-kernel, linux-doc,
Pratyush Mallick
From: Pratyush Mallick <pratmal@google.com>
Currently, the free page reporting uses a hardcoded delay of
(2 HZ) between reporting intervals. While this is a reasonable
default, it lacks the flexibility to adapt to varying guest workloads.
A low delay allows aggressive memory reclamation, returning unused
pages to the host as quickly as possible. However, during spiky
allocation/free churn, this immediate reporting can lead to a severe
performance penalty (nested page faults) as the guest re-allocates memory
that the host has just unmapped. In these scenarios, there is benefit
from increasing the delay to batch free pages over a longer window,
absorbing the churn without hypercall and re-fault overhead.
This patch exposes the delay as a module parameter:
/sys/module/page_reporting/parameters/page_reporting_delay_ms, measured
in milliseconds and defaults to 2000ms.
Signed-off-by: Pratyush Mallick <pratmal@google.com>
---
v3:
- Converted page_reporting_delay_ms from a sysctl to a module parameter.
- Dropped the max value cap (PAGE_REPORTING_DELAY_MS_MAX).
- Documented page_reporting_delay_ms in kernel-parameters.txt.
- Updated code comments in mm/page_reporting.c.
- v2: https://lore.kernel.org/linux-mm/3da27fde-25dc-4cb8-8e05-74cd26fc2f7c@kernel.org/T/#t
v2:
- Documented page_reporting_delay_ms in Documentation/admin-guide/sysctl/vm.rst.
- v1: https://lore.kernel.org/linux-mm/20260722192935.1646848-1-pratmal@google.com/T/#u
v1: Fixed feedback from RFC.
- Added lower and upper cap to sysctl value.
- Reverted the reordering on page_reporting_delay_ms.
- Dropped the mod_delayed_work() change.
- RFC: https://lore.kernel.org/linux-mm/20260714171456.2350037-1-pratmal@google.com/T/#u
.../admin-guide/kernel-parameters.txt | 6 ++++++
mm/page_reporting.c | 21 ++++++++++++-------
2 files changed, 19 insertions(+), 8 deletions(-)
diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index b5493a7f8f22..364c2dce8e70 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -4810,6 +4810,12 @@ Kernel parameters
Adjust the minimal page reporting order. The page
reporting is disabled when it exceeds MAX_PAGE_ORDER.
+ page_reporting.page_reporting_delay_ms=
+ [KNL] Free page reporting delay in milliseconds
+ Format: <unsigned integer>
+ Adjust the delay in milliseconds between free page
+ reporting intervals. Default is 2000 (2 seconds).
+
panic= [KNL] Kernel behaviour on panic: delay <timeout>
timeout > 0: seconds before rebooting
timeout = 0: wait forever
diff --git a/mm/page_reporting.c b/mm/page_reporting.c
index 942e84b6908a..a67311468204 100644
--- a/mm/page_reporting.c
+++ b/mm/page_reporting.c
@@ -47,7 +47,11 @@ MODULE_PARM_DESC(page_reporting_order, "Set page reporting order");
*/
EXPORT_SYMBOL_GPL(page_reporting_order);
-#define PAGE_REPORTING_DELAY (2 * HZ)
+static unsigned int page_reporting_delay_ms = 2 * MSEC_PER_SEC;
+module_param(page_reporting_delay_ms, uint, 0644);
+MODULE_PARM_DESC(page_reporting_delay_ms,
+ "Set page reporting delay in milliseconds");
+
static struct page_reporting_dev_info __rcu *pr_dev_info __read_mostly;
enum {
@@ -76,11 +80,11 @@ __page_reporting_request(struct page_reporting_dev_info *prdev)
return;
/*
- * Delay the start of work to allow a sizable queue to build. For
- * now we are limiting this to running no more than once every
- * couple of seconds.
+ * Delay the start of work to allow a sizable queue to build.
+ * We limit this based on page_reporting_delay_ms.
*/
- schedule_delayed_work(&prdev->work, PAGE_REPORTING_DELAY);
+ schedule_delayed_work(&prdev->work,
+ msecs_to_jiffies(page_reporting_delay_ms));
}
/* notify prdev of free page reporting request */
@@ -335,12 +339,13 @@ static void page_reporting_process(struct work_struct *work)
err_out:
/*
* If the state has reverted back to requested then there may be
- * additional pages to be processed. We will defer for 2s to allow
- * more pages to accumulate.
+ * additional pages to be processed. We will defer by
+ * page_reporting_delay_ms to allow more pages to accumulate.
*/
state = atomic_cmpxchg(&prdev->state, state, PAGE_REPORTING_IDLE);
if (state == PAGE_REPORTING_REQUESTED)
- schedule_delayed_work(&prdev->work, PAGE_REPORTING_DELAY);
+ schedule_delayed_work(&prdev->work,
+ msecs_to_jiffies(page_reporting_delay_ms));
}
static DEFINE_MUTEX(page_reporting_mutex);
--
2.55.0.229.g6434b31f56-goog
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH v3] mm/page_reporting: Add page_reporting_delay_ms module parameter
2026-07-27 23:05 [PATCH v3] mm/page_reporting: Add page_reporting_delay_ms module parameter pratmal
@ 2026-07-27 23:59 ` SJ Park
2026-07-28 1:13 ` Andrew Morton
1 sibling, 0 replies; 3+ messages in thread
From: SJ Park @ 2026-07-27 23:59 UTC (permalink / raw)
To: pratmal
Cc: SJ Park, akpm, vbabka, david, corbet, skhan, anshuman.khandual,
gthelen, surenb, mhocko, jackmanb, hannes, ziy, ljs, liam, rppt,
linux-mm, linux-kernel, linux-doc
On Mon, 27 Jul 2026 23:05:45 +0000 pratmal@google.com wrote:
> From: Pratyush Mallick <pratmal@google.com>
>
> Currently, the free page reporting uses a hardcoded delay of
> (2 HZ) between reporting intervals. While this is a reasonable
> default, it lacks the flexibility to adapt to varying guest workloads.
>
> A low delay allows aggressive memory reclamation, returning unused
> pages to the host as quickly as possible. However, during spiky
> allocation/free churn, this immediate reporting can lead to a severe
> performance penalty (nested page faults) as the guest re-allocates memory
> that the host has just unmapped. In these scenarios, there is benefit
> from increasing the delay to batch free pages over a longer window,
> absorbing the churn without hypercall and re-fault overhead.
>
> This patch exposes the delay as a module parameter:
> /sys/module/page_reporting/parameters/page_reporting_delay_ms, measured
> in milliseconds and defaults to 2000ms.
Makes sense to me.
>
> Signed-off-by: Pratyush Mallick <pratmal@google.com>
Reviewed-by: SJ Park <sj@kernel.org>
Thanks,
SJ
[...]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v3] mm/page_reporting: Add page_reporting_delay_ms module parameter
2026-07-27 23:05 [PATCH v3] mm/page_reporting: Add page_reporting_delay_ms module parameter pratmal
2026-07-27 23:59 ` SJ Park
@ 2026-07-28 1:13 ` Andrew Morton
1 sibling, 0 replies; 3+ messages in thread
From: Andrew Morton @ 2026-07-28 1:13 UTC (permalink / raw)
To: pratmal
Cc: vbabka, david, sj, corbet, skhan, anshuman.khandual, gthelen,
surenb, mhocko, jackmanb, hannes, ziy, ljs, liam, rppt, linux-mm,
linux-kernel, linux-doc, Link Lin
On Mon, 27 Jul 2026 23:05:45 +0000 pratmal@google.com wrote:
> From: Pratyush Mallick <pratmal@google.com>
>
> Currently, the free page reporting uses a hardcoded delay of
> (2 HZ) between reporting intervals. While this is a reasonable
> default, it lacks the flexibility to adapt to varying guest workloads.
>
> A low delay allows aggressive memory reclamation, returning unused
> pages to the host as quickly as possible. However, during spiky
> allocation/free churn, this immediate reporting can lead to a severe
> performance penalty (nested page faults) as the guest re-allocates memory
> that the host has just unmapped. In these scenarios, there is benefit
> from increasing the delay to batch free pages over a longer window,
> absorbing the churn without hypercall and re-fault overhead.
>
> This patch exposes the delay as a module parameter:
> /sys/module/page_reporting/parameters/page_reporting_delay_ms, measured
> in milliseconds and defaults to 2000ms.
Of course we'd prefer some sort of self-tuning so the kernel
automatically avoids the situation. But the user's expectation that
reporting occurs at a fixed frequency messes up that concept.
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
lgtm. It conflicts with Link Lin's "mm/page_reporting: use
system_freezable_wq to fix UAF during suspend". Easy resolution:
Documentation/admin-guide/kernel-parameters.txt | 6 ++++
mm/page_reporting.c | 19 ++++++++------
2 files changed, 17 insertions(+), 8 deletions(-)
--- a/Documentation/admin-guide/kernel-parameters.txt~mm-page_reporting-add-page_reporting_delay_ms-module-parameter
+++ a/Documentation/admin-guide/kernel-parameters.txt
@@ -4813,6 +4813,12 @@ Kernel parameters
Adjust the minimal page reporting order. The page
reporting is disabled when it exceeds MAX_PAGE_ORDER.
+ page_reporting.page_reporting_delay_ms=
+ [KNL] Free page reporting delay in milliseconds
+ Format: <unsigned integer>
+ Adjust the delay in milliseconds between free page
+ reporting intervals. Default is 2000 (2 seconds).
+
panic= [KNL] Kernel behaviour on panic: delay <timeout>
timeout > 0: seconds before rebooting
timeout = 0: wait forever
--- a/mm/page_reporting.c~mm-page_reporting-add-page_reporting_delay_ms-module-parameter
+++ a/mm/page_reporting.c
@@ -48,7 +48,11 @@ MODULE_PARM_DESC(page_reporting_order, "
*/
EXPORT_SYMBOL_GPL(page_reporting_order);
-#define PAGE_REPORTING_DELAY (2 * HZ)
+static unsigned int page_reporting_delay_ms = 2 * MSEC_PER_SEC;
+module_param(page_reporting_delay_ms, uint, 0644);
+MODULE_PARM_DESC(page_reporting_delay_ms,
+ "Set page reporting delay in milliseconds");
+
static struct page_reporting_dev_info __rcu *pr_dev_info __read_mostly;
enum {
@@ -77,12 +81,11 @@ __page_reporting_request(struct page_rep
return;
/*
- * Delay the start of work to allow a sizable queue to build. For
- * now we are limiting this to running no more than once every
- * couple of seconds.
+ * Delay the start of work to allow a sizable queue to build.
+ * We limit this based on page_reporting_delay_ms.
*/
queue_delayed_work(system_freezable_wq, &prdev->work,
- PAGE_REPORTING_DELAY);
+ msecs_to_jiffies(page_reporting_delay_ms));
}
/* notify prdev of free page reporting request */
@@ -337,13 +340,13 @@ static void page_reporting_process(struc
err_out:
/*
* If the state has reverted back to requested then there may be
- * additional pages to be processed. We will defer for 2s to allow
- * more pages to accumulate.
+ * additional pages to be processed. We will defer by
+ * page_reporting_delay_ms to allow more pages to accumulate.
*/
state = atomic_cmpxchg(&prdev->state, state, PAGE_REPORTING_IDLE);
if (state == PAGE_REPORTING_REQUESTED)
queue_delayed_work(system_freezable_wq, &prdev->work,
- PAGE_REPORTING_DELAY);
+ msecs_to_jiffies(page_reporting_delay_ms));
}
static DEFINE_MUTEX(page_reporting_mutex);
_
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-07-28 1:13 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-27 23:05 [PATCH v3] mm/page_reporting: Add page_reporting_delay_ms module parameter pratmal
2026-07-27 23:59 ` SJ Park
2026-07-28 1:13 ` Andrew Morton
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox