Re: [PATCH 1/3] mm: move internal mempolicy APIs to new internal header
Matthew Wilcox <[email protected]> Thu, 16 Jul 2026 17:48:11 +0100
| 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 02:30:10PM +0000, Brendan Jackman wrote: > There are no external users for this surface, reduce the scope. > -struct folio *folio_alloc_mpol_noprof(gfp_t gfp, unsigned int order, > - struct mempolicy *mpol, pgoff_t ilx, int nid); Hm. So what we're saying is that allocations which respect mempolicy are only for core mm and not for, eg, device drivers to do. Is that really what we want to say? I don't think so, because that's inconsistent with having just widened __filemap_get_folio_mpol to allow guest_memfd to specify a mempolicy.