Re: [PATCH] mm/page_alloc: let the bulk and folio allocators carry alloc_flags

[Gregory Price <gourry@gourry.net>]

On Fri, Oct 02, 2026 at 11:52:22AM +0100, Brendan Jackman wrote:
> On Mon Sep 14, 2026 at 5:54 PM BST, Gregory Price wrote:
> >> Brendan this will conflict mildly with your ALLOC_UNMAPPED work,
> >> because you add an init_alloc_flags call in alloc_pages_bulk_noprof :
> >> https://lore.kernel.org/linux-mm/20260726-page_alloc-unmapped-v3-20-6f5729aa9832@google.com/
> >> 
> >> I wanted to pull this out ahead to try to deal with the conflict.
> >> 
> >
> > Sashiko pointed out some issues that arise from rebasing on the recent
> > ALLOC_NOLOCK work, and in a quick review I found a similar slow-path
> > fallback issue with the NOBLOCK patch separate of this patch.
> >
> > Brendan, if you're alright with it, can I pull the NOBLOCK patch out
> > ahead into a 2-commit series and I'll add the small fixups?
> 
> Hey, sorry about the silence I let LKML pile up rather badly, it's been
> quite a month..
> 
> Yes I am totally alright with this (glad to see you went ahead).

See: https://lore.kernel.org/linux-mm/20260923211041.3127588-1-gourry@gourry.net/

for the RFC that pulls everything out ahead.

I figured out how to make-do without it for the first go-around of
private nodes, but it would still be needed (in some form) if mempolicy
support makes its way into the private nodes series in the future - so i
think we should still discuss it.

~Gregory