From: Christoph Hellwig <hch@lst.de>
To: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: minor sb clearing improvements
Date: Mon, 21 Nov 2022 18:47:47 +0100 [thread overview]
Message-ID: <20221121174749.387407-1-hch@lst.de> (raw)
Hi all,
this series moves btrfs off the deprecated write_one_page API that
requires ->writepage to be implemented (in this case on the block
device inode), and while doing so also avoids a pointless sb read
for zoned file systems.
Diffstat:
volumes.c | 50 +++++++++++++++++++++++++-------------------------
1 file changed, 25 insertions(+), 25 deletions(-)
next reply other threads:[~2022-11-21 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 17:47 Christoph Hellwig [this message]
2022-11-21 17:47 ` [PATCH 1/2] btrfs: don't read the disk superblock for zoned devices in btrfs_scratch_superblocks Christoph Hellwig
2022-11-22 11:39 ` Johannes Thumshirn
2022-11-21 17:47 ` [PATCH 2/2] btrfs: stop using write_one_page in btrfs_scratch_superblock Christoph Hellwig
2023-01-09 20:15 ` minor sb clearing improvements 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=20221121174749.387407-1-hch@lst.de \
--to=hch@lst.de \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.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).