From: Johannes Thumshirn <johannes.thumshirn@wdc.com>
To: David Sterba <dsterba@suse.com>
Cc: Nikolay Borisov <nborisov@suse.com>,
"linux-btrfs @ vger . kernel . org" <linux-btrfs@vger.kernel.org>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: [PATCH v2 0/6] btrfs: remove buffer heads form superblock handling
Date: Thu, 23 Jan 2020 17:18:43 +0900 [thread overview]
Message-ID: <20200123081849.23397-1-johannes.thumshirn@wdc.com> (raw)
This patch series removes the use of buffer_heads from btrfs' super block read
and write paths. It also converts the integrity-checking code to only work
with pages and BIOs.
Compared to buffer heads, this gives us a leaner call path, as the
buffer_head code wraps around getting pages from the page-cache and adding
them to BIOs to submit.
The first patch is from Nikolay and exports btrfs_release_disk_super(), so it
can be used in the patchews follwing in this series.
The second patch removes buffer_heads from superblock reading.
The third from super_block writing and the subsequent patches remove the
buffer_heads from the integrity check code.
It's based on misc-next from Wednesday January 22, and doesn't show any
regressions in xfstests to the baseline.
Cahnges to v1:
- Added patch #1
- Converted sb reading and integrity checking to use the page cache
- Added rationale behind the conversion to the commit messages.
- For more details see the idividual patches.
Johannes Thumshirn (5):
btrfs: remove buffer heads from super block reading
btrfs: remove use of buffer_heads from superblock writeout
btrfs: remove btrfsic_submit_bh()
btrfs: remove buffer_heads from btrfsic_process_written_block()
btrfs: remove buffer_heads form superblock mirror integrity checking
Nikolay Borisov (1):
btrfs: export btrfs_release_disk_super
fs/btrfs/check-integrity.c | 204 ++++++++++---------------------------
fs/btrfs/check-integrity.h | 2 -
fs/btrfs/disk-io.c | 194 +++++++++++++++++++++--------------
fs/btrfs/disk-io.h | 4 +-
fs/btrfs/volumes.c | 64 +++++++-----
fs/btrfs/volumes.h | 3 +-
6 files changed, 216 insertions(+), 255 deletions(-)
--
2.24.1
next reply other threads:[~2020-01-23 8:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 8:18 Johannes Thumshirn [this message]
2020-01-23 8:18 ` [PATCH v2 1/6] btrfs: export btrfs_release_disk_super Johannes Thumshirn
2020-01-23 13:42 ` Josef Bacik
2020-01-23 8:18 ` [PATCH v2 2/6] btrfs: remove buffer heads from super block reading Johannes Thumshirn
2020-01-23 13:51 ` Josef Bacik
2020-01-23 13:53 ` Johannes Thumshirn
2020-01-23 14:13 ` Nikolay Borisov
2020-01-23 16:45 ` Johannes Thumshirn
2020-01-23 22:25 ` David Sterba
2020-01-24 13:54 ` David Sterba
2020-01-24 14:03 ` David Sterba
2020-01-23 8:18 ` [PATCH v2 3/6] btrfs: remove use of buffer_heads from superblock writeout Johannes Thumshirn
2020-01-23 13:59 ` Josef Bacik
2020-01-23 14:19 ` Nikolay Borisov
2020-01-24 14:15 ` David Sterba
2020-01-23 8:18 ` [PATCH v2 4/6] btrfs: remove btrfsic_submit_bh() Johannes Thumshirn
2020-01-23 14:00 ` Josef Bacik
2020-01-23 8:18 ` [PATCH v2 5/6] btrfs: remove buffer_heads from btrfsic_process_written_block() Johannes Thumshirn
2020-01-23 14:00 ` Josef Bacik
2020-01-23 8:18 ` [PATCH v2 6/6] btrfs: remove buffer_heads form superblock mirror integrity checking Johannes Thumshirn
2020-01-23 14:03 ` Josef Bacik
2020-01-23 14:23 ` Nikolay Borisov
2020-01-24 14:22 ` David Sterba
2020-01-24 14:59 ` 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=20200123081849.23397-1-johannes.thumshirn@wdc.com \
--to=johannes.thumshirn@wdc.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@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 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.