Re: [PATCH 1/3] mm: move internal mempolicy APIs to new internal header
"Brendan Jackman" <[email protected]> Thu, 16 Jul 2026 16:04:30 +0000
| Newsgroups | dev.linux.lists.loongarch,dev.linux.lists.iommu,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-kernel,org.kernel.vger.linux-nfs,org.kernel.vger.netdev,org.kvack.linux-mm |
|---|---|
| Message-ID | <[email protected]> |
On Thu Jul 16, 2026 at 3:22 PM UTC, Vlastimil Babka (SUSE) wrote: > On 7/16/26 16:30, Brendan Jackman wrote: >> There are no external users for this surface, reduce the scope. >> >> Ulterior motive: a later patch will add an alloc_flags arg to some parts >> of this. >> >> Note it might seem like this could just go in internal.h, since it's >> pretty small, but actually it will eventually need to import >> page_alloc.h, we don't want to import that from internal.h so best to >> proactively created this header now. > > Hmm, maybe it could just go to page_alloc.h then? After all this is just > bunch of internal page allocation functions, which just take the mempolicy > pointer? That would work AFAICS, but I think it's quite tidy that, currently, all functions declared in page_alloc.h are defined in page_alloc.c. This would break that. If you're certain you don't care about that then I could live with using page_alloc.h.