linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v2 0/2] mm/compaction: allow more aggressive proactive compaction
@ 2025-01-27 21:46 Michal Clapinski
  2025-01-27 21:46 ` [PATCH v2 1/2] mm/compaction: remove low watermark cap for " Michal Clapinski
  2025-01-27 21:46 ` [PATCH v2 2/2] mm/compaction: make proactive compaction high watermark configurable via sysctl Michal Clapinski
  0 siblings, 2 replies; 3+ messages in thread
From: Michal Clapinski @ 2025-01-27 21:46 UTC (permalink / raw)
  To: Andrew Morton, Vlastimil Babka, Pasha Tatashin
  Cc: linux-mm, linux-kernel, Michal Clapinski

Our goal is to keep memory usage of a VM low on the host. For that
reason, we use free page reporting which by default reports free pages
of order 9 and larger to the host to be freed. The feature works well
only if the memory in the guest is not fragmented below pages of order
9. Proactive compaction can be reused to achieve defragmentation after
some parameter tweaking.

When the fragmentation score (lower is better) gets larger than the
high watermark, proactive compaction kicks in. Compaction stops when
the score goes below the low watermark (or no progress is made and
backoff kicks in). Let's define the difference between high and low
watermarks as leeway. Before these changes, the minimum possible value
for low watermark was 5 and the leeway was hardcoded to 10 (so minimum
possible value for high watermark was 15).

v2: Change commit msgs and document the new sysctl.

Michal Clapinski (2):
  mm/compaction: remove low watermark cap for proactive compaction
  mm/compaction: make proactive compaction high watermark configurable
    via sysctl

 Documentation/admin-guide/sysctl/vm.rst | 17 +++++++++++++++++
 mm/compaction.c                         | 14 ++++++++++++--
 2 files changed, 29 insertions(+), 2 deletions(-)

-- 
2.48.1.262.g85cc9f2d1e-goog



^ permalink raw reply	[flat|nested] 3+ messages in thread

* [PATCH v2 1/2] mm/compaction: remove low watermark cap for proactive compaction
  2025-01-27 21:46 [PATCH v2 0/2] mm/compaction: allow more aggressive proactive compaction Michal Clapinski
@ 2025-01-27 21:46 ` Michal Clapinski
  2025-01-27 21:46 ` [PATCH v2 2/2] mm/compaction: make proactive compaction high watermark configurable via sysctl Michal Clapinski
  1 sibling, 0 replies; 3+ messages in thread
From: Michal Clapinski @ 2025-01-27 21:46 UTC (permalink / raw)
  To: Andrew Morton, Vlastimil Babka, Pasha Tatashin
  Cc: linux-mm, linux-kernel, Michal Clapinski

Previously a min cap of 5 has been set in the commit introducing
proactive compaction. This was to make sure users don't hurt themselves
by setting the proactiveness to 100 and making their system
unresponsive. But the compaction mechanism has a backoff mechanism that
will sleep for 30s if no progress is made, so I don't see a significant
risk here. My system (20GB of memory) has been perfectly fine with
proactiveness set to 100 and leeway set to 0.

Signed-off-by: Michal Clapinski <mclapinski@google.com>
Change-Id: I007e3a02d126d3858ceecf5ce57a1c360177c37b
---
 mm/compaction.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mm/compaction.c b/mm/compaction.c
index a2b16b08cbbff..29524242a16ef 100644
--- a/mm/compaction.c
+++ b/mm/compaction.c
@@ -2253,7 +2253,7 @@ static unsigned int fragmentation_score_wmark(bool low)
 	 * activity in case a user sets the proactiveness tunable
 	 * close to 100 (maximum).
 	 */
-	wmark_low = max(100U - sysctl_compaction_proactiveness, 5U);
+	wmark_low = 100U - sysctl_compaction_proactiveness;
 	return low ? wmark_low : min(wmark_low + 10, 100U);
 }
 
-- 
2.48.1.262.g85cc9f2d1e-goog



^ permalink raw reply	[flat|nested] 3+ messages in thread

* [PATCH v2 2/2] mm/compaction: make proactive compaction high watermark configurable via sysctl
  2025-01-27 21:46 [PATCH v2 0/2] mm/compaction: allow more aggressive proactive compaction Michal Clapinski
  2025-01-27 21:46 ` [PATCH v2 1/2] mm/compaction: remove low watermark cap for " Michal Clapinski
@ 2025-01-27 21:46 ` Michal Clapinski
  1 sibling, 0 replies; 3+ messages in thread
From: Michal Clapinski @ 2025-01-27 21:46 UTC (permalink / raw)
  To: Andrew Morton, Vlastimil Babka, Pasha Tatashin
  Cc: linux-mm, linux-kernel, Michal Clapinski

Currently, the difference between the high and low watermarks for
proactive compaction is hardcoded to 10. This hardcoded difference is
too large for free page reporting to work well.

Add a new sysctl, `compaction_proactiveness_leeway`, to control the
difference between the high and low watermarks.

Signed-off-by: Michal Clapinski <mclapinski@google.com>
Change-Id: I4fecd273e9ac55a3e75770ff18c53d5db6acf1ff
---
 Documentation/admin-guide/sysctl/vm.rst | 17 +++++++++++++++++
 mm/compaction.c                         | 12 +++++++++++-
 2 files changed, 28 insertions(+), 1 deletion(-)

diff --git a/Documentation/admin-guide/sysctl/vm.rst b/Documentation/admin-guide/sysctl/vm.rst
index f48eaa98d22d2..ec6343ee4248d 100644
--- a/Documentation/admin-guide/sysctl/vm.rst
+++ b/Documentation/admin-guide/sysctl/vm.rst
@@ -27,6 +27,7 @@ Currently, these files are in /proc/sys/vm:
 - admin_reserve_kbytes
 - compact_memory
 - compaction_proactiveness
+- compaction_proactiveness_leeway
 - compact_unevictable_allowed
 - dirty_background_bytes
 - dirty_background_ratio
@@ -133,6 +134,22 @@ proactive compaction is not being effective.
 Be careful when setting it to extreme values like 100, as that may
 cause excessive background compaction activity.
 
+compaction_proactiveness_leeway
+===============================
+
+This tunable controls the difference between high and low watermarks for
+proactive compaction. This tunable takes a value in the range [0, 100] with
+a default value of 10. Higher values will result in proactive compaction
+triggering less often but doing more work when it does trigger.
+
+Proactive compaction triggers when fragmentation score (lower is better) gets
+larger than high watermark. Compaction stops when the score gets smaller or
+equal to low watermark (or when no progress is being made).
+The watermarks are calculated as follows:
+
+low_wmark = 100 - compaction_proactiveness;
+high_wmark = low_wmark + compaction_proactiveness_leeway;
+
 compact_unevictable_allowed
 ===========================
 
diff --git a/mm/compaction.c b/mm/compaction.c
index 29524242a16ef..fd546b797e544 100644
--- a/mm/compaction.c
+++ b/mm/compaction.c
@@ -1921,6 +1921,7 @@ static int sysctl_compact_unevictable_allowed __read_mostly = CONFIG_COMPACT_UNE
  * background. It takes values in the range [0, 100].
  */
 static unsigned int __read_mostly sysctl_compaction_proactiveness = 20;
+static unsigned int __read_mostly sysctl_compaction_proactiveness_leeway = 10;
 static int sysctl_extfrag_threshold = 500;
 static int __read_mostly sysctl_compact_memory;
 
@@ -2254,7 +2255,7 @@ static unsigned int fragmentation_score_wmark(bool low)
 	 * close to 100 (maximum).
 	 */
 	wmark_low = 100U - sysctl_compaction_proactiveness;
-	return low ? wmark_low : min(wmark_low + 10, 100U);
+	return low ? wmark_low : min(wmark_low + sysctl_compaction_proactiveness_leeway, 100U);
 }
 
 static bool should_proactive_compact_node(pg_data_t *pgdat)
@@ -3314,6 +3315,15 @@ static struct ctl_table vm_compaction[] = {
 		.extra1		= SYSCTL_ZERO,
 		.extra2		= SYSCTL_ONE_HUNDRED,
 	},
+	{
+		.procname	= "compaction_proactiveness_leeway",
+		.data		= &sysctl_compaction_proactiveness_leeway,
+		.maxlen		= sizeof(sysctl_compaction_proactiveness_leeway),
+		.mode		= 0644,
+		.proc_handler	= compaction_proactiveness_sysctl_handler,
+		.extra1		= SYSCTL_ZERO,
+		.extra2		= SYSCTL_ONE_HUNDRED,
+	},
 	{
 		.procname	= "extfrag_threshold",
 		.data		= &sysctl_extfrag_threshold,
-- 
2.48.1.262.g85cc9f2d1e-goog



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2025-01-27 21:47 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-01-27 21:46 [PATCH v2 0/2] mm/compaction: allow more aggressive proactive compaction Michal Clapinski
2025-01-27 21:46 ` [PATCH v2 1/2] mm/compaction: remove low watermark cap for " Michal Clapinski
2025-01-27 21:46 ` [PATCH v2 2/2] mm/compaction: make proactive compaction high watermark configurable via sysctl Michal Clapinski

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox