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.

Michal Clapinski (2):
  mm/compaction: remove low watermark cap for proactive compaction
  mm/compaction: expose a new param for proactive compaction

 mm/compaction.c | 14 ++++++++++++--
 1 file changed, 12 insertions(+), 2 deletions(-)

-- 
2.48.1.262.g85cc9f2d1e-goog

On 1/24/25 19:21, Michal Clapinski wrote:
> 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.

Could you explain the tweaking more in the cover letter? You seem to be
allowing proactive compaction to kick in more aggressively but at the same
time lower the leeway to make it finish quicker?

Thanks.

> Michal Clapinski (2):
>   mm/compaction: remove low watermark cap for proactive compaction
>   mm/compaction: expose a new param for proactive compaction
> 
>  mm/compaction.c | 14 ++++++++++++--
>  1 file changed, 12 insertions(+), 2 deletions(-)
>