From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/3] btrfs: small cleanups mostly for subpage cases
Date: Tue, 30 May 2023 09:45:26 +0800 [thread overview]
Message-ID: <cover.1685411033.git.wqu@suse.com> (raw)
Changelog:
v2:
- Fix an offset-by-one bug in the 3rd patch
Unlock extent range end is inclusive.
During my hunt on the subpage uptodate desync bugs reported from Matt, I
exposed several PageUptodate usage which results inefficiency for
subpage cases.
Those two are fixed in the first two patches.
Furthermore I found processed_extent infrastructure is no longer needed
especially after all the csum verification is moved to storage layer (or
bio.c inside btrfs), we can easily unlock the full range without the
need for the infrastructure.
Thus the last patch would delete the processed_extent infrastructure
completely.
Qu Wenruo (3):
btrfs: make alloc_extent_buffer() handle previously uptodate range
more efficient for subpage
btrfs: use the same @uptodate variable for end_bio_extent_readpage()
btrfs: remove processed_extent infrastructure
fs/btrfs/extent_io.c | 89 +++++---------------------------------------
1 file changed, 10 insertions(+), 79 deletions(-)
--
2.40.1
next reply other threads:[~2023-05-30 1:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 1:45 Qu Wenruo [this message]
2023-05-30 1:45 ` [PATCH v2 1/3] btrfs: make alloc_extent_buffer() handle previously uptodate range more efficient for subpage Qu Wenruo
2023-05-30 5:41 ` Christoph Hellwig
2023-05-30 1:45 ` [PATCH v2 2/3] btrfs: use the same @uptodate variable for end_bio_extent_readpage() Qu Wenruo
2023-05-30 5:41 ` Christoph Hellwig
2023-05-30 6:06 ` Anand Jain
2023-05-30 1:45 ` [PATCH v2 3/3] btrfs: remove processed_extent infrastructure Qu Wenruo
2023-05-30 5:43 ` Christoph Hellwig
2023-05-30 6:19 ` Qu Wenruo
2023-05-30 23:35 ` Qu Wenruo
2023-05-31 4:33 ` Christoph Hellwig
2023-05-30 12:48 ` [PATCH v2 0/3] btrfs: small cleanups mostly for subpage 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.1685411033.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.