From: Matthew Wilcox <willy@infradead.org>
To: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Amir Goldstein <amir73il@gmail.com>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
lsf-pc <lsf-pc@lists.linux-foundation.org>,
Gregory Price <gourry@gourry.net>,
Bharata B Rao <bharata@amd.com>,
Donet Tom <donettom@linux.ibm.com>,
Aboorva Devarajan <aboorvad@linux.ibm.com>,
linux-mm@kvack.org, Ojaswin Mujoo <ojaswin@linux.ibm.com>
Subject: Re: [LSF/MM/BPF BoF Session] Numa-Aware Placement for Page Cache Pages
Date: Thu, 30 Apr 2026 14:15:19 +0100 [thread overview]
Message-ID: <afNV5wbhsFQJLzxi@casper.infradead.org> (raw)
In-Reply-To: <h5ossmwe.ritesh.list@gmail.com>
On Thu, Apr 30, 2026 at 05:03:37PM +0530, Ritesh Harjani (IBM) wrote:
> Linux already supports memory tiers and there are ongoing discussions around
> promotion of unmapped page cache pages, which lets kernel do the right thing
> for userspace page cache pages on a tiered system.
Well, you know my opinion of that idea ...
> So the question is:
> Do we need a userspace interface for the placement policy of page cache pages on a per file basis?
What do we do if two tasks both "know" the right NUMA placement for the
inode's data, and they disagree?
> 1. Is there a need for an interface that allows userspace to do per-fd page
> placement and maybe per-fd page migration?
Ideally, no, the kernel should observe the task and get it right.
By the way, you're familiar with how filemap_alloc_folio_noprof()
works today, right? I forget whether cpuset_do_page_mem_spread
is on or off by default.
> Let me know if people think that this discussion qualifies for a BoF discussion at LSFMM?
> Or do you think it's a bad idea altogether, if that is the case - Then
> please help me understand, why so?
> Before starting to jump on the implemention of any of this - I would
> like to gather feedback on what do others think?
I'm just concerned about what other session i'll have to miss to attend
this instead ;-)
next prev parent reply other threads:[~2026-04-30 13:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 11:33 [LSF/MM/BPF BoF Session] Numa-Aware Placement for Page Cache Pages Ritesh Harjani (IBM)
2026-04-30 13:15 ` Matthew Wilcox [this message]
2026-04-30 14:43 ` Ritesh Harjani
2026-05-02 14:57 ` Gregory Price
2026-05-02 15:49 ` Gregory Price
2026-05-03 16:18 ` Ritesh Harjani
2026-05-03 23:48 ` Gregory Price
2026-05-02 23:00 ` Matthew Wilcox
2026-05-03 14:15 ` Gregory Price
2026-04-30 17:32 ` Gregory Price
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=afNV5wbhsFQJLzxi@casper.infradead.org \
--to=willy@infradead.org \
--cc=aboorvad@linux.ibm.com \
--cc=amir73il@gmail.com \
--cc=bharata@amd.com \
--cc=brauner@kernel.org \
--cc=donettom@linux.ibm.com \
--cc=gourry@gourry.net \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@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