From: Matthew Wilcox <willy@infradead.org>
To: Shivank Garg <shivankg@amd.com>
Cc: kent.overstreet@linux.dev, clm@fb.com, josef@toxicpanda.com,
dsterba@suse.com, xiang@kernel.org, chao@kernel.org,
jaegeuk@kernel.org, akpm@linux-foundation.org, david@redhat.com,
vbabka@suse.cz, zbestahu@gmail.com, jefflexu@linux.alibaba.com,
dhavale@google.com, lihongbo22@huawei.com, pankaj.gupta@amd.com,
linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-btrfs@vger.kernel.org, linux-erofs@lists.ozlabs.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
kvm@vger.kernel.org, linux-coco@lists.linux.dev
Subject: Re: [PATCH V2 1/2] mm/filemap: Add NUMA mempolicy support to filemap_alloc_folio()
Date: Mon, 23 Jun 2025 13:22:58 +0100 [thread overview]
Message-ID: <aFlHIjLBwn3LQFMC@casper.infradead.org> (raw)
In-Reply-To: <20250623093939.1323623-4-shivankg@amd.com>
On Mon, Jun 23, 2025 at 09:39:41AM +0000, Shivank Garg wrote:
> From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
>
> Add a mempolicy parameter to filemap_alloc_folio() to enable NUMA-aware
> page cache allocations. This will be used by upcoming changes to
> support NUMA policies in guest-memfd, where guest_memory needs to be
> allocated according to NUMA policy specified by the VMM.
>
> All existing users pass NULL maintaining current behavior.
I don't want to see this as a separate series. I want to see it as part
of the series that introduces the user.
Andrew, please drop these two patches from your tree.
prev parent reply other threads:[~2025-06-23 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 9:39 [PATCH V2 1/2] mm/filemap: Add NUMA mempolicy support to filemap_alloc_folio() Shivank Garg
2025-06-23 9:39 ` [PATCH V2 2/2] mm/filemap: Extend __filemap_get_folio() to support NUMA memory policies Shivank Garg
2025-06-23 12:22 ` Matthew Wilcox [this message]
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=aFlHIjLBwn3LQFMC@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=chao@kernel.org \
--cc=clm@fb.com \
--cc=david@redhat.com \
--cc=dhavale@google.com \
--cc=dsterba@suse.com \
--cc=jaegeuk@kernel.org \
--cc=jefflexu@linux.alibaba.com \
--cc=josef@toxicpanda.com \
--cc=kent.overstreet@linux.dev \
--cc=kvm@vger.kernel.org \
--cc=lihongbo22@huawei.com \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pankaj.gupta@amd.com \
--cc=shivankg@amd.com \
--cc=vbabka@suse.cz \
--cc=xiang@kernel.org \
--cc=zbestahu@gmail.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;
as well as URLs for NNTP newsgroup(s).