public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs: get rid of compressed_bio::compressed_folios[] part 1
Date: Tue, 20 Jan 2026 10:30:07 +1030	[thread overview]
Message-ID: <cover.1768866942.git.wqu@suse.com> (raw)

Currently we have compressed_bio::compressed_folios[] allowing us to do
random access to any compressed folio, then we queue all folios in that
array into a real btrfs_bio, and submit that btrfs_bio for read/write.

However there is not really any need to do random access of that array.

All compression/decompression is doing sequential folio access.

The part 1 is some easy and safe conversion on decompression path.

The part 2 will handle the compression part, but unfortunately that will
require some changes all compression path, thus will need some extra
work.

And only after compression paths also got converted, we still need
that compressed_folios[] array for now.

Qu Wenruo (3):
  btrfs: use folio_iter to handle lzo_decompress_bio()
  btrfs: use folio_iter to handle zlib_decompress_bio()
  btrfs: use folio_iter to handle zstd_decompress_bio()

 fs/btrfs/lzo.c  | 48 +++++++++++++++++++++++++++++++++++++++---------
 fs/btrfs/zlib.c | 19 ++++++++++++-------
 fs/btrfs/zstd.c | 13 +++++++++----
 3 files changed, 60 insertions(+), 20 deletions(-)

-- 
2.52.0


             reply	other threads:[~2026-01-20  0:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20  0:00 Qu Wenruo [this message]
2026-01-20  0:00 ` [PATCH 1/3] btrfs: use folio_iter to handle lzo_decompress_bio() Qu Wenruo
2026-01-20  0:00 ` [PATCH 2/3] btrfs: use folio_iter to handle zlib_decompress_bio() Qu Wenruo
2026-01-20  0:00 ` [PATCH 3/3] btrfs: use folio_iter to handle zstd_decompress_bio() Qu Wenruo
2026-01-20 17:29 ` [PATCH 0/3] btrfs: get rid of compressed_bio::compressed_folios[] part 1 David Sterba
2026-01-20 20:41   ` Qu Wenruo
2026-01-21  3:47     ` David Sterba
2026-01-21  3:47 ` David Sterba
2026-01-24 21:48 ` Qu Wenruo

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.1768866942.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