From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: fujunjie <fujunjie1@qq.com>, Andrew Morton <akpm@linux-foundation.org>
Cc: Brendan Jackman <jackmanb@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.com>,
Suren Baghdasaryan <surenb@google.com>, Zi Yan <ziy@nvidia.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Charan Teja Kalla <charante@codeaurora.org>,
David Rientjes <rientjes@google.com>
Subject: Re: [PATCH] mm/page_alloc: fix deferred compaction accounting
Date: Thu, 28 May 2026 16:29:26 +0200 [thread overview]
Message-ID: <d1fdfb33-12b8-48f8-bd0f-c9d90407a2e1@kernel.org> (raw)
In-Reply-To: <tencent_368AF1F3821E46232637BE16D65C45CF3308@qq.com>
On 5/26/26 11:12, fujunjie wrote:
> COMPACT_DEFERRED means compaction did not start because past failures
> caused the zone to be deferred. try_to_compact_pages() returns the
> maximum result seen while walking the zonelist, so a final
> COMPACT_DEFERRED result means no later zone reported that compaction
> actually ran.
>
> __alloc_pages_direct_compact() skips COMPACTSTALL and COMPACTFAIL
> accounting when try_to_compact_pages() returns COMPACT_SKIPPED, but not
> when it returns COMPACT_DEFERRED. A deferred-only direct compaction
> attempt can therefore look like a stall, and then a failure if the
> allocation still cannot be satisfied.
>
> Treat COMPACT_DEFERRED like COMPACT_SKIPPED in this accounting path. If
> a later zone runs compaction and returns a result above COMPACT_DEFERRED,
> or compact_zone_order() reports COMPACT_SUCCESS for a captured page, the
> final result is not COMPACT_DEFERRED and the existing accounting still
> runs.
>
> Signed-off-by: fujunjie <fujunjie1@qq.com>
Hm I wonder why didn't we do that right away in 06dac2f467fe ("mm:
compaction: update the COMPACT[STALL|FAIL] events properly"), seems like
even back then there was nothing that would e.g. convert _DEFERED to
_SKIPPED from try_to_compact_pages(), and the changelog did mention deferred.
So I guess for posterity we could do (but no Cc: stable, it's just stats).
Fixes: 06dac2f467fe ("mm: compaction: update the COMPACT[STALL|FAIL] events
properly")
Reviewed-by: Vlastimil Babka (SUSE) <vbabka@kernel.org>
Thanks!
> ---
> mm/page_alloc.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 23c7298d3be2..ddeb79fa12db 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -4161,7 +4161,8 @@ __alloc_pages_direct_compact(gfp_t gfp_mask, unsigned int order,
> psi_memstall_leave(&pflags);
> delayacct_compact_end();
>
> - if (*compact_result == COMPACT_SKIPPED)
> + if (*compact_result == COMPACT_SKIPPED ||
> + *compact_result == COMPACT_DEFERRED)
> return NULL;
> /*
> * At least in one zone compaction wasn't deferred or skipped, so let's
>
> base-commit: e8c2f9fdadee7cbc75134dc463c1e0d856d6e5c7
prev parent reply other threads:[~2026-05-28 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 9:12 fujunjie
2026-05-28 14:29 ` Vlastimil Babka (SUSE) [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=d1fdfb33-12b8-48f8-bd0f-c9d90407a2e1@kernel.org \
--to=vbabka@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=charante@codeaurora.org \
--cc=fujunjie1@qq.com \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=rientjes@google.com \
--cc=surenb@google.com \
--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®