linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@kernel.org>
To: Ryan Roberts <ryan.roberts@arm.com>
Cc: 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>,
	Barry Song <baohua@kernel.org>,  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: Wed, 17 Dec 2025 11:21:42 -0800	[thread overview]
Message-ID: <873458zzg9.fsf@linux.intel.com> (raw)
In-Reply-To: <20240717071257.4141363-1-ryan.roberts@arm.com> (Ryan Roberts's message of "Wed, 17 Jul 2024 08:12:52 +0100")

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?

Thanks,
-Andi


  parent reply	other threads:[~2025-12-17 19:21 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 [this message]
2025-12-18  4:50   ` Barry Song

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=873458zzg9.fsf@linux.intel.com \
    --to=ak@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=baohua@kernel.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