From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH] mm/readahead: add a desired folio order for readhead
Date: Fri, 21 Nov 2025 18:03:44 +0000 [thread overview]
Message-ID: <aSCpgMvrvA_hR4VB@google.com> (raw)
In-Reply-To: <aSB3kcsneAS94DgU@casper.infradead.org>
On 11/21, Matthew Wilcox wrote:
> On Fri, Nov 21, 2025 at 01:48:11AM +0000, Jaegeuk Kim wrote:
> > This patch adds a desired folio order in file_ra_state in order to get
> > non-zero-order allocation for readahead.
>
> Why? Does it not ramp up quickly enough for you?
>
> I see a lot of patches from you that say what the patch does but very
> little about why. Please explain yourself more.
Yeah, let me revisit the patches and post another version that uplifts
code into mm/fs with what I'm trying to address.
prev parent reply other threads:[~2025-11-21 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 1:48 [PATCH] mm/readahead: add a desired folio order for readhead Jaegeuk Kim
2025-11-21 14:30 ` Matthew Wilcox
2025-11-21 18:03 ` Jaegeuk Kim [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=aSCpgMvrvA_hR4VB@google.com \
--to=jaegeuk@kernel.org \
--cc=david@redhat.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--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