From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH 00/10] btrfs: clean up zoned device helpers
Date: Wed, 14 Sep 2022 19:07:40 -0400 [thread overview]
Message-ID: <cover.1663196746.git.josef@toxicpanda.com> (raw)
Hello,
This is in the same vein as my other cleanups, however zoned has a lot of
different patches so I'm sending them as a group, additionally so I get the
appropriate review attention from the right people.
These cleanups are aimed at making any helpers inside of zoned.h only derefence
structs that are declared inside of zoned.h, which is just
btrfs_zoned_device_info. This means moving helpers that aren't used anywhere
else into their respective C files, reworking some of the helpers, and other
related cleanups. Thanks,
Josef
Josef Bacik (10):
btrfs: add a helper for opening a new device to add to the fs
btrfs: move btrfs_check_device_zone_type into volumes.c
btrfs: move btrfs_can_zone_reset into extent-tree.c
btrfs: move btrfs_check_super_location into scrub.c
btrfs: move btrfs_zoned_meta_io_*lock to extent_io.c
btrfs: move btrfs_clear_treelog_bg to extent-tree.c
btrfs: move btrfs_zoned_data_reloc_*lock to extent_io.c
btrfs: move btrfs_zoned_bg_is_full into block-group.c
btrfs: make the zoned helpers take btrfs_zoned_device_info
btrfs: delete btrfs_check_super_location helper
fs/btrfs/block-group.c | 6 +++
fs/btrfs/block-group.h | 1 +
fs/btrfs/dev-replace.c | 10 +---
fs/btrfs/extent-tree.c | 27 ++++++++++
fs/btrfs/extent_io.c | 30 +++++++++++
fs/btrfs/scrub.c | 8 +--
fs/btrfs/volumes.c | 49 ++++++++++++++---
fs/btrfs/volumes.h | 2 +
fs/btrfs/zoned.c | 20 +++----
fs/btrfs/zoned.h | 118 +++++------------------------------------
10 files changed, 136 insertions(+), 135 deletions(-)
--
2.26.3
next reply other threads:[~2022-09-14 23:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 23:07 Josef Bacik [this message]
2022-09-14 23:07 ` [PATCH 01/10] btrfs: add a helper for opening a new device to add to the fs Josef Bacik
2022-09-15 13:54 ` Johannes Thumshirn
2022-09-21 9:39 ` Pankaj Raghav
2022-09-14 23:07 ` [PATCH 02/10] btrfs: move btrfs_check_device_zone_type into volumes.c Josef Bacik
2022-09-15 13:55 ` Johannes Thumshirn
2022-09-14 23:07 ` [PATCH 03/10] btrfs: move btrfs_can_zone_reset into extent-tree.c Josef Bacik
2022-09-15 13:56 ` Johannes Thumshirn
2022-09-14 23:07 ` [PATCH 04/10] btrfs: move btrfs_check_super_location into scrub.c Josef Bacik
2022-09-15 13:57 ` Johannes Thumshirn
2022-09-14 23:07 ` [PATCH 05/10] btrfs: move btrfs_zoned_meta_io_*lock to extent_io.c Josef Bacik
2022-09-15 13:58 ` Johannes Thumshirn
2022-09-14 23:07 ` [PATCH 06/10] btrfs: move btrfs_clear_treelog_bg to extent-tree.c Josef Bacik
2022-09-15 14:00 ` Johannes Thumshirn
2022-09-14 23:07 ` [PATCH 07/10] btrfs: move btrfs_zoned_data_reloc_*lock to extent_io.c Josef Bacik
2022-09-15 14:01 ` Johannes Thumshirn
2022-09-14 23:07 ` [PATCH 08/10] btrfs: move btrfs_zoned_bg_is_full into block-group.c Josef Bacik
2022-09-15 14:02 ` Johannes Thumshirn
2022-09-14 23:07 ` [PATCH 09/10] btrfs: make the zoned helpers take btrfs_zoned_device_info Josef Bacik
2022-09-15 14:05 ` Johannes Thumshirn
2022-09-14 23:07 ` [PATCH 10/10] btrfs: delete btrfs_check_super_location helper Josef Bacik
2022-09-15 7:29 ` Naohiro Aota
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.1663196746.git.josef@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=kernel-team@fb.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