From: Vlastimil Babka <vbabka@suse.cz>
To: Baolin Wang <baolin.wang@linux.alibaba.com>,
akpm@linux-foundation.org, Zi Yan <ziy@nvidia.com>
Cc: mgorman@techsingularity.net, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mm: compaction: limit the suitable target page order to be less than cc->order
Date: Mon, 12 Feb 2024 10:13:56 +0100 [thread overview]
Message-ID: <20c8fa7c-62ae-4e48-aaec-8b512519cee9@suse.cz> (raw)
In-Reply-To: <afcd9377351c259df7a25a388a4a0d5862b986f4.1705928395.git.baolin.wang@linux.alibaba.com>
On 1/22/24 14:01, Baolin Wang wrote:
> It can not improve the fragmentation if we isolate the target free pages
> exceeding cc->order, especially when the cc->order is less than pageblock_order.
> For example, suppose the pageblock_order is MAX_ORDER (size is 4M) and cc->order
> is 2M THP size, we should not isolate other 2M free pages to be the migration
> target, which can not improve the fragmentation.
>
> Moreover this is also applicable for large folio compaction.
So why not Cc: Zi Yan? (done)
> Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
I doubt this will make much difference, because if such a larger order free
page exists, we shouldn't have a reason to be compacting for a lower order
in the first place?
> ---
> mm/compaction.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/mm/compaction.c b/mm/compaction.c
> index 27ada42924d5..066b72b3471a 100644
> --- a/mm/compaction.c
> +++ b/mm/compaction.c
> @@ -1346,12 +1346,14 @@ static bool suitable_migration_target(struct compact_control *cc,
> {
> /* If the page is a large free page, then disallow migration */
> if (PageBuddy(page)) {
> + int order = cc->order > 0 ? cc->order : pageblock_order;
> +
> /*
> * We are checking page_order without zone->lock taken. But
> * the only small danger is that we skip a potentially suitable
> * pageblock, so it's not worth to check order for valid range.
> */
> - if (buddy_order_unsafe(page) >= pageblock_order)
> + if (buddy_order_unsafe(page) >= order)
> return false;
> }
>
next prev parent reply other threads:[~2024-02-12 9:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 13:01 Baolin Wang
2024-01-22 13:01 ` [PATCH 2/2] mm: compaction: update the cc->nr_migratepages when allocating or freeing the freepages Baolin Wang
2024-02-01 10:30 ` Mel Gorman
2024-02-12 10:32 ` Vlastimil Babka
2024-02-19 2:34 ` Baolin Wang
2024-02-01 10:29 ` [PATCH 1/2] mm: compaction: limit the suitable target page order to be less than cc->order Mel Gorman
2024-02-12 9:13 ` Vlastimil Babka [this message]
2024-02-12 15:00 ` Zi Yan
2024-02-19 2:55 ` Baolin Wang
2024-02-21 22:15 ` Andrew Morton
2024-02-21 22:22 ` Vlastimil Babka
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=20c8fa7c-62ae-4e48-aaec-8b512519cee9@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--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
all inboxes | Powered by JetHome®