From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Qiqi Liu <liuqiqi@kylinos.cn>, akpm@linux-foundation.org
Cc: surenb@google.com, mhocko@suse.com, brendan.jackman@linux.dev,
hannes@cmpxchg.org, ziy@nvidia.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] mm/page_alloc: apply per-task GFP context in bulk allocator
Date: Mon, 14 Sep 2026 15:01:14 +0200 [thread overview]
Message-ID: <b932c690-7ab0-4521-a7d2-5ed5130379b8@kernel.org> (raw)
In-Reply-To: <20260914080451.294896-1-liuqiqi@kylinos.cn>
On 9/14/26 10:04, Qiqi Liu wrote:
> alloc_pages_bulk_noprof() does not call current_gfp_context(), so
> per-task scoped allocation constraints (PF_MEMALLOC_NOIO,
> PF_MEMALLOC_NOFS, PF_MEMALLOC_PIN) are not applied on the bulk fast
> path.
>
> The most direct consequence is PF_MEMALLOC_PIN: without clearing
I'd say ignoring PF_MEMALLOC_NOFS/PF_MEMALLOC_NOIO also can have a direct
consequence?
Let's replace the line above with:
By ignoring PF_MEMALLOC_NOIO and PF_MEMALLOC_NOFS, the allocation can
theoretically result in a deadlock.
Ignoring PF_MEMALLOC_PIN also has consequences: without clearing ...
> __GFP_MOVABLE, prepare_alloc_pages() selects MIGRATE_MOVABLE for
> the PCP list, and a task with PF_MEMALLOC_PIN set receives movable
> pages from the bulk allocator. Once pinned, these pages can no
> longer be migrated but remain in MOVABLE pageblocks, violating the
> mobility contract. This can increase fragmentation and interfere
> with compaction or contiguous-memory allocations, eventually
> surfacing as higher allocation latency or allocation failures under
> memory pressure.
>
> Found via review of the bulk allocation tracepoint hooks [1].
>
> [1] https://lore.kernel.org/all/20260907120949.418450-1-liuqiqi@kylinos.cn/
> Link: https://sashiko.dev/#/patchset/20260907120949.418450-1-liuqiqi%40kylinos.cn
> Fixes: 387ba26fb1cb ("mm/page_alloc: add a bulk page allocator")
> Cc: stable@vger.kernel.org
> Signed-off-by: Qiqi Liu <liuqiqi@kylinos.cn>
LGTM.
Reviewed-by: Vlastimil Babka (SUSE) <vbabka@kernel.org>
> ---
> mm/page_alloc.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 12fac9084c48..3be7288a1aa7 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -5207,6 +5207,7 @@ unsigned long alloc_pages_bulk_noprof(gfp_t gfp, int preferred_nid,
>
> /* May set ALLOC_NOFRAGMENT, fragmentation will return 1 page. */
> gfp &= gfp_allowed_mask;
> + gfp = current_gfp_context(gfp);
> if (!prepare_alloc_pages(gfp, 0, preferred_nid, nodemask, &ac, &gfp, &alloc_flags))
> goto out;
>
next prev parent reply other threads:[~2026-09-14 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 8:04 Qiqi Liu
2026-09-14 13:01 ` Vlastimil Babka (SUSE) [this message]
2026-09-15 7:42 ` Qiqi Liu
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=b932c690-7ab0-4521-a7d2-5ed5130379b8@kernel.org \
--to=vbabka@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brendan.jackman@linux.dev \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuqiqi@kylinos.cn \
--cc=mhocko@suse.com \
--cc=stable@vger.kernel.org \
--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®