From: Vlastimil Babka <vbabka@suse.cz>
To: Michal Clapinski <mclapinski@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Nitin Gupta <nigupta@nvidia.com>,
Pasha Tatashin <tatashin@google.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] mm/compaction: allow more aggressive proactive compaction
Date: Mon, 27 Jan 2025 11:36:23 +0100 [thread overview]
Message-ID: <642c9896-cfd8-4d98-9ab4-f9bd548db481@suse.cz> (raw)
In-Reply-To: <20250124182140.2243862-1-mclapinski@google.com>
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(-)
>
prev parent reply other threads:[~2025-01-27 10:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 18:21 Michal Clapinski
2025-01-24 18:21 ` [PATCH 1/2] mm/compaction: remove low watermark cap for " Michal Clapinski
2025-01-25 16:03 ` Pasha Tatashin
2025-01-27 10:38 ` Vlastimil Babka
2025-01-27 13:31 ` Michał Cłapiński
2025-01-27 14:13 ` Vlastimil Babka
2025-01-24 18:21 ` [PATCH 2/2] mm/compaction: expose a new param " Michal Clapinski
2025-01-25 16:20 ` Pasha Tatashin
2025-01-27 10:40 ` Vlastimil Babka
2025-01-27 10:36 ` Vlastimil Babka [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=642c9896-cfd8-4d98-9ab4-f9bd548db481@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mclapinski@google.com \
--cc=nigupta@nvidia.com \
--cc=tatashin@google.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