On 6/18/25 13:29, Shivank Garg wrote: > From: Shivansh Dhiman <shivansh.dhiman@xxxxxxx> > > Add NUMA mempolicy support to the filemap allocation path by introducing > new APIs that take a mempolicy argument: > - filemap_grab_folio_mpol() > - filemap_alloc_folio_mpol() > - __filemap_get_folio_mpol() > > These APIs allow callers to specify a NUMA policy during page cache > allocations, enabling fine-grained control over memory placement. This is > particularly needed by KVM when using guest-memfd memory backends, where > the guest memory needs to be allocated according to the NUMA policy > specified by VMM. > > The existing non-mempolicy APIs remain unchanged and continue to use the > default allocation behavior. > > Signed-off-by: Shivansh Dhiman <shivansh.dhiman@xxxxxxx> > Co-developed-by: Shivank Garg <shivankg@xxxxxxx> > Signed-off-by: Shivank Garg <shivankg@xxxxxxx> I think __filemap_get_folio() could become a static inline wrapper for __filemap_get_folio_mpol in pagemap.h. Otherwise, Acked-by: Vlastimil Babka <vbabka@xxxxxxx>
