From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
Qu Wenruo <wqu@suse.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Cc: "josef@toxicpanda.com" <josef@toxicpanda.com>
Subject: Re: [PATCH v4 2/6] btrfs: lock subpage ranges in one go for writepage_delalloc()
Date: Mon, 13 May 2024 07:39:59 +0930 [thread overview]
Message-ID: <56cf6f8b-f035-4324-8f6a-05221cdcca4d@gmx.com> (raw)
In-Reply-To: <84a9472d-87b0-41dc-a8dc-b9c644e81b53@wdc.com>
在 2024/5/13 02:38, Johannes Thumshirn 写道:
> Why do we even need this patch in the first place, when we're basically
> reverting it again in Patch 4/6?
Indeed, I'll merge this patch into 4/6.
Thanks,
Qu
next prev parent reply other threads:[~2024-05-12 22:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 0:15 [PATCH v4 0/6] btrfs: subpage + zoned fixes Qu Wenruo
2024-05-11 0:15 ` [PATCH v4 1/6] btrfs: make __extent_writepage_io() to write specified range only Qu Wenruo
2024-05-12 16:31 ` Johannes Thumshirn
2024-05-11 0:15 ` [PATCH v4 2/6] btrfs: lock subpage ranges in one go for writepage_delalloc() Qu Wenruo
2024-05-12 17:08 ` Johannes Thumshirn
2024-05-12 22:09 ` Qu Wenruo [this message]
2024-05-11 0:15 ` [PATCH v4 3/6] btrfs: subpage: introduce helpers to handle subpage delalloc locking Qu Wenruo
2024-05-12 17:10 ` Johannes Thumshirn
2024-05-11 0:15 ` [PATCH v4 4/6] btrfs: migrate writepage_delalloc() to use subpage helpers Qu Wenruo
2024-05-12 17:14 ` Johannes Thumshirn
2024-05-11 0:15 ` [PATCH v4 5/6] btrfs: do not clear page dirty inside extent_write_locked_range() Qu Wenruo
2024-05-12 17:19 ` Johannes Thumshirn
2024-05-11 0:15 ` [PATCH v4 6/6] btrfs: make extent_write_locked_range() to handle subpage writeback correctly Qu Wenruo
2024-05-12 17:21 ` Johannes Thumshirn
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=56cf6f8b-f035-4324-8f6a-05221cdcca4d@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.com \
/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).