From: Barry Song <21cnbao@gmail.com>
To: Andi Kleen <ak@kernel.org>
Cc: Ryan Roberts <ryan.roberts@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
Jonathan Corbet <corbet@lwn.net>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
David Hildenbrand <david@redhat.com>,
Lance Yang <ioworker0@gmail.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Gavin Shan <gshan@redhat.com>,
Pankaj Raghav <kernel@pankajraghav.com>,
Daniel Gomez <da.gomez@samsung.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC PATCH v1 0/4] Control folio sizes used for page cache memory
Date: Thu, 18 Dec 2025 12:50:54 +0800 [thread overview]
Message-ID: <CAGsJ_4xhL89OSrqZitmdVPFDBbdU+AP-UeeHNoef3uRhnL8RLA@mail.gmail.com> (raw)
In-Reply-To: <873458zzg9.fsf@linux.intel.com>
On Thu, Dec 18, 2025 at 3:21 AM Andi Kleen <ak@kernel.org> wrote:
>
> Ryan Roberts <ryan.roberts@arm.com> writes:
>
> > Hi All,
> >
> > This series is an RFC that adds sysfs and kernel cmdline controls to configure
> > the set of allowed large folio sizes that can be used when allocating
> > file-memory for the page cache. As part of the control mechanism, it provides
> > for a special-case "preferred folio size for executable mappings" marker.
> >
> > I'm trying to solve 2 separate problems with this series:
> >
>
> What happened to this patchkit? I was looking into how to efficiently
> get larger pages for text transparently, and there doesn't seem
> to be anything better than such a heuristic?
I do feel that we need some controls over file folio sizes.
It could also be implemented using an eBPF-based approach, such as [1]?
[1] https://lore.kernel.org/linux-mm/20251026100159.6103-1-laoar.shao@gmail.com/
Thanks
Barry
prev parent reply other threads:[~2025-12-18 4:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 7:12 Ryan Roberts
2024-07-17 7:12 ` [RFC PATCH v1 1/4] mm: mTHP user controls to configure pagecache large folio sizes Ryan Roberts
2024-07-17 7:12 ` [RFC PATCH v1 2/4] mm: Introduce "always+exec" for mTHP file_enabled control Ryan Roberts
2024-07-17 17:10 ` Ryan Roberts
2024-07-17 7:12 ` [RFC PATCH v1 3/4] mm: Override mTHP "enabled" defaults at kernel cmdline Ryan Roberts
2024-07-19 0:46 ` Barry Song
2024-07-19 7:47 ` Ryan Roberts
2024-07-19 7:52 ` Barry Song
2024-07-19 8:18 ` Ryan Roberts
2024-07-19 8:29 ` David Hildenbrand
2024-07-22 9:13 ` Daniel Gomez
2024-07-22 9:36 ` Ryan Roberts
2024-07-22 14:10 ` Ryan Roberts
2024-07-17 7:12 ` [RFC PATCH v1 4/4] mm: Override mTHP "file_enabled" " Ryan Roberts
2024-07-17 10:31 ` [RFC PATCH v1 0/4] Control folio sizes used for page cache memory David Hildenbrand
2024-07-17 10:45 ` Ryan Roberts
2024-07-17 14:25 ` David Hildenbrand
2024-07-22 9:35 ` Daniel Gomez
2024-07-22 9:43 ` Ryan Roberts
[not found] ` <480f34d0-a943-40da-9c69-2353fe311cf7@arm.com>
2024-09-19 8:20 ` Barry Song
2024-09-19 17:21 ` Ryan Roberts
2024-12-06 5:09 ` Barry Song
2024-12-06 5:29 ` Baolin Wang
2025-12-17 19:21 ` Andi Kleen
2025-12-18 4:50 ` Barry Song [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=CAGsJ_4xhL89OSrqZitmdVPFDBbdU+AP-UeeHNoef3uRhnL8RLA@mail.gmail.com \
--to=21cnbao@gmail.com \
--cc=ak@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=corbet@lwn.net \
--cc=da.gomez@samsung.com \
--cc=david@redhat.com \
--cc=gshan@redhat.com \
--cc=hughd@google.com \
--cc=ioworker0@gmail.com \
--cc=kernel@pankajraghav.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=willy@infradead.org \
/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