Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: properly enable compressed readahead for bs < ps and large folio cases
Date: Sun, 26 Apr 2026 17:21:02 +0930	[thread overview]
Message-ID: <cover.1777189624.git.wqu@suse.com> (raw)

Compressed data readahead is disabled for bs < ps cases, but it has
never taken large folios into the consideration.

And that unexpectedly enables compressed data readahead for large
folios, which should go through the same subpage routine.

This means for real bs < ps cases compressed data read is disabled, but
still enabled for bs == ps with large folios.

This small series will properly enable the compressed readahead for both
bs < ps and large folios cases, mostly by simply remove the unnecessary
checks.

Then since we're here, also update the function name and comments to
reflect that we're already using folio interface, not the old page
interface.

Qu Wenruo (2):
  btrfs: enable cross-folio readahead for bs < ps and large folio cases
  btrfs: refresh add_ra_bio_pages() to indicate it's using folios

 fs/btrfs/compression.c | 67 +++++++++++++++---------------------------
 1 file changed, 24 insertions(+), 43 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-04-26  7:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-26  7:51 Qu Wenruo [this message]
2026-04-26  7:51 ` [PATCH 1/2] btrfs: enable cross-folio readahead for bs < ps and large folio cases Qu Wenruo
2026-04-27 13:21   ` David Sterba
2026-04-27 21:54     ` Qu Wenruo
2026-04-28  3:53       ` David Sterba
2026-04-26  7:51 ` [PATCH 2/2] btrfs: refresh add_ra_bio_pages() to indicate it's using folios Qu Wenruo
2026-04-27 13:37   ` David Sterba
2026-04-27 13:38 ` [PATCH 0/2] btrfs: properly enable compressed readahead for bs < ps and large folio cases David Sterba

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=cover.1777189624.git.wqu@suse.com \
    --to=wqu@suse.com \
    --cc=linux-btrfs@vger.kernel.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