From: Ge Yang <yangge1116@126.com>
To: akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
21cnbao@gmail.com, david@redhat.com,
baolin.wang@linux.alibaba.com, hannes@cmpxchg.org,
vbabka@suse.cz, liuzixing@hygon.cn
Subject: Re: [PATCH V2] mm: compaction: use the actual allocation context to determine the watermarks for costly order during async memory compaction
Date: Tue, 21 Jan 2025 18:01:42 +0800 [thread overview]
Message-ID: <4ad51644-92de-47ca-af2a-bcb1866059d2@126.com> (raw)
In-Reply-To: <1736991214-29069-1-git-send-email-yangge1116@126.com>
This patch has been revised based on Vlastimil's suggestions. Please
continue to review it. Thank you.
在 2025/1/16 9:33, yangge1116@126.com 写道:
> From: yangge <yangge1116@126.com>
>
> There are 4 NUMA nodes on my machine, and each NUMA node has 32GB
> of memory. I have configured 16GB of CMA memory on each NUMA node,
> and starting a 32GB virtual machine with device passthrough is
> extremely slow, taking almost an hour.
>
> Long term GUP cannot allocate memory from CMA area, so a maximum of
> 16 GB of no-CMA memory on a NUMA node can be used as virtual machine
> memory. There is 16GB of free CMA memory on a NUMA node, which is
> sufficient to pass the order-0 watermark check, causing the
> __compaction_suitable() function to consistently return true.
>
> For costly allocations, if the __compaction_suitable() function always
> returns true, it causes the __alloc_pages_slowpath() function to fail
> to exit at the appropriate point. This prevents timely fallback to
> allocating memory on other nodes, ultimately resulting in excessively
> long virtual machine startup times.
> Call trace:
> __alloc_pages_slowpath
> if (compact_result == COMPACT_SKIPPED ||
> compact_result == COMPACT_DEFERRED)
> goto nopage; // should exit __alloc_pages_slowpath() from here
>
> We could use the real unmovable allocation context to have
> __zone_watermark_unusable_free() subtract CMA pages, and thus we won't
> pass the order-0 check anymore once the non-CMA part is exhausted. There
> is some risk that in some different scenario the compaction could in
> fact migrate pages from the exhausted non-CMA part of the zone to the
> CMA part and succeed, and we'll skip it instead. But only __GFP_NORETRY
> allocations should be affected in the immediate "goto nopage" when
> compaction is skipped, others will attempt with DEF_COMPACT_PRIORITY
> anyway and won't fail without trying to compact-migrate the non-CMA
> pageblocks into CMA pageblocks first, so it should be fine.
>
> After this fix, it only takes a few tens of seconds to start a 32GB
> virtual machine with device passthrough functionality.
>
> Link: https://lore.kernel.org/lkml/1736335854-548-1-git-send-email-yangge1116@126.com/
> Signed-off-by: yangge <yangge1116@126.com>
> Acked-by: Vlastimil Babka <vbabka@suse.cz>
> ---
>
> V2:
> - update code and message suggested by Vlastimil
>
> mm/compaction.c | 29 +++++++++++++++++++++++++----
> 1 file changed, 25 insertions(+), 4 deletions(-)
>
> diff --git a/mm/compaction.c b/mm/compaction.c
> index 07bd227..3de7b67 100644
> --- a/mm/compaction.c
> +++ b/mm/compaction.c
> @@ -2490,7 +2490,8 @@ bool compaction_zonelist_suitable(struct alloc_context *ac, int order,
> */
> static enum compact_result
> compaction_suit_allocation_order(struct zone *zone, unsigned int order,
> - int highest_zoneidx, unsigned int alloc_flags)
> + int highest_zoneidx, unsigned int alloc_flags,
> + bool async)
> {
> unsigned long watermark;
>
> @@ -2499,6 +2500,23 @@ compaction_suit_allocation_order(struct zone *zone, unsigned int order,
> alloc_flags))
> return COMPACT_SUCCESS;
>
> + /*
> + * For unmovable allocations (without ALLOC_CMA), check if there is enough
> + * free memory in the non-CMA pageblocks. Otherwise compaction could form
> + * the high-order page in CMA pageblocks, which would not help the
> + * allocation to succeed. However, limit the check to costly order async
> + * compaction (such as opportunistic THP attempts) because there is the
> + * possibility that compaction would migrate pages from non-CMA to CMA
> + * pageblock.
> + */
> + if (order > PAGE_ALLOC_COSTLY_ORDER && async &&
> + !(alloc_flags & ALLOC_CMA)) {
> + watermark = low_wmark_pages(zone) + compact_gap(order);
> + if (!__zone_watermark_ok(zone, 0, watermark, highest_zoneidx,
> + 0, zone_page_state(zone, NR_FREE_PAGES)))
> + return COMPACT_SKIPPED;
> + }
> +
> if (!compaction_suitable(zone, order, highest_zoneidx))
> return COMPACT_SKIPPED;
>
> @@ -2534,7 +2552,8 @@ compact_zone(struct compact_control *cc, struct capture_control *capc)
> if (!is_via_compact_memory(cc->order)) {
> ret = compaction_suit_allocation_order(cc->zone, cc->order,
> cc->highest_zoneidx,
> - cc->alloc_flags);
> + cc->alloc_flags,
> + cc->mode == MIGRATE_ASYNC);
> if (ret != COMPACT_CONTINUE)
> return ret;
> }
> @@ -3037,7 +3056,8 @@ static bool kcompactd_node_suitable(pg_data_t *pgdat)
>
> ret = compaction_suit_allocation_order(zone,
> pgdat->kcompactd_max_order,
> - highest_zoneidx, ALLOC_WMARK_MIN);
> + highest_zoneidx, ALLOC_WMARK_MIN,
> + false);
> if (ret == COMPACT_CONTINUE)
> return true;
> }
> @@ -3078,7 +3098,8 @@ static void kcompactd_do_work(pg_data_t *pgdat)
> continue;
>
> ret = compaction_suit_allocation_order(zone,
> - cc.order, zoneid, ALLOC_WMARK_MIN);
> + cc.order, zoneid, ALLOC_WMARK_MIN,
> + false);
> if (ret != COMPACT_CONTINUE)
> continue;
>
next prev parent reply other threads:[~2025-01-21 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 1:33 yangge1116
2025-01-21 10:01 ` Ge Yang [this message]
2025-01-22 7:19 ` Baolin Wang
2025-01-22 14:42 ` Johannes Weiner
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=4ad51644-92de-47ca-af2a-bcb1866059d2@126.com \
--to=yangge1116@126.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuzixing@hygon.cn \
--cc=vbabka@suse.cz \
/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