From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/4] btrfs: the missing 4 patches to implement metadata write path
Date: Tue, 6 Apr 2021 08:35:59 +0800 [thread overview]
Message-ID: <20210406003603.64381-1-wqu@suse.com> (raw)
When adding the comments for subpage metadata code, I inserted the
comment patch into the wrong position, and then use that patch as a
separator between data and metadata write path.
Thus the submitted metadata write path patchset lacks the real functions
to submit subpage metadata write bio.
Qu Wenruo (4):
btrfs: introduce end_bio_subpage_eb_writepage() function
btrfs: introduce write_one_subpage_eb() function
btrfs: make lock_extent_buffer_for_io() to be subpage compatible
btrfs: introduce submit_eb_subpage() to submit a subpage metadata page
fs/btrfs/extent_io.c | 293 ++++++++++++++++++++++++++++++++++++++-----
1 file changed, 263 insertions(+), 30 deletions(-)
--
2.31.1
next reply other threads:[~2021-04-06 0:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 0:35 Qu Wenruo [this message]
2021-04-06 0:36 ` [PATCH 1/4] btrfs: introduce end_bio_subpage_eb_writepage() function Qu Wenruo
2021-04-06 0:36 ` [PATCH 2/4] btrfs: introduce write_one_subpage_eb() function Qu Wenruo
2021-04-06 0:36 ` [PATCH 3/4] btrfs: make lock_extent_buffer_for_io() to be subpage compatible Qu Wenruo
2021-04-06 0:36 ` [PATCH 4/4] btrfs: introduce submit_eb_subpage() to submit a subpage metadata page Qu Wenruo
2021-04-23 11:29 ` [PATCH 0/4] btrfs: the missing 4 patches to implement metadata write path David Sterba
2021-04-23 11:36 ` Qu Wenruo
2021-04-23 20:31 ` David Sterba
2021-04-23 22:34 ` 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=20210406003603.64381-1-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;
as well as URLs for NNTP newsgroup(s).