From: David Sterba <dsterba@suse.cz>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>, Christoph Hellwig <hch@lst.de>,
Naohiro Aota <naohiro.aota@wdc.com>, Qu Wenruo <wqu@suse.com>,
Damien Le Moal <dlemoal@kernel.org>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 08/11] btrfs: add raid stripe tree pretty printer
Date: Tue, 12 Sep 2023 22:42:39 +0200 [thread overview]
Message-ID: <20230912204239.GF20408@twin.jikos.cz> (raw)
In-Reply-To: <20230911-raid-stripe-tree-v8-8-647676fa852c@wdc.com>
On Mon, Sep 11, 2023 at 05:52:09AM -0700, Johannes Thumshirn wrote:
> Decode raid-stripe-tree entries on btrfs_print_tree().
>
> Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
> ---
> fs/btrfs/print-tree.c | 49 +++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 49 insertions(+)
>
> diff --git a/fs/btrfs/print-tree.c b/fs/btrfs/print-tree.c
> index 0c93439e929f..f01919e4bb37 100644
> --- a/fs/btrfs/print-tree.c
> +++ b/fs/btrfs/print-tree.c
> @@ -9,6 +9,7 @@
> #include "print-tree.h"
> #include "accessors.h"
> #include "tree-checker.h"
> +#include "raid-stripe-tree.h"
>
> struct root_name_map {
> u64 id;
> @@ -28,6 +29,7 @@ static const struct root_name_map root_map[] = {
> { BTRFS_FREE_SPACE_TREE_OBJECTID, "FREE_SPACE_TREE" },
> { BTRFS_BLOCK_GROUP_TREE_OBJECTID, "BLOCK_GROUP_TREE" },
> { BTRFS_DATA_RELOC_TREE_OBJECTID, "DATA_RELOC_TREE" },
> + { BTRFS_RAID_STRIPE_TREE_OBJECTID, "RAID_STRIPE_TREE" },
> };
>
> const char *btrfs_root_name(const struct btrfs_key *key, char *buf)
> @@ -189,6 +191,48 @@ static void print_uuid_item(const struct extent_buffer *l, unsigned long offset,
> }
> }
>
> +struct raid_encoding_map {
> + u8 encoding;
> + char name[16];
> +};
> +
> +static const struct raid_encoding_map raid_map[] = {
> + { BTRFS_STRIPE_DUP, "DUP" },
> + { BTRFS_STRIPE_RAID0, "RAID0" },
> + { BTRFS_STRIPE_RAID1, "RAID1" },
> + { BTRFS_STRIPE_RAID1C3, "RAID1C3" },
> + { BTRFS_STRIPE_RAID1C4, "RAID1C4" },
> + { BTRFS_STRIPE_RAID5, "RAID5" },
> + { BTRFS_STRIPE_RAID6, "RAID6" },
> + { BTRFS_STRIPE_RAID10, "RAID10" }
> +};
Instead of another table tranlating constants to raid names, can you
somehow utilize the btrfs_raid_array table? If the STRIPE values match
the RAID (the indexes to the table) you could add a simple wrapper.
> +
> +static const char *stripe_encoding_name(u8 encoding)
> +{
> + for (int i = 0; i < ARRAY_SIZE(raid_map); i++) {
> + if (raid_map[i].encoding == encoding)
> + return raid_map[i].name;
> + }
> +
> + return "UNKNOWN";
> +}
> +
> +static void print_raid_stripe_key(const struct extent_buffer *eb, u32 item_size,
> + struct btrfs_stripe_extent *stripe)
> +{
> + int num_stripes = btrfs_num_raid_stripes(item_size);
> + u8 encoding = btrfs_stripe_extent_encoding(eb, stripe);
> + int i;
> +
> + pr_info("\t\t\tencoding: %s\n", stripe_encoding_name(encoding));
> +
> + for (i = 0; i < num_stripes; i++)
> + pr_info("\t\t\tstride %d devid %llu physical %llu length %llu\n",
> + i, btrfs_raid_stride_devid(eb, &stripe->strides[i]),
> + btrfs_raid_stride_physical(eb, &stripe->strides[i]),
> + btrfs_raid_stride_length(eb, &stripe->strides[i]));
> +}
> +
> /*
> * Helper to output refs and locking status of extent buffer. Useful to debug
> * race condition related problems.
> @@ -349,6 +393,11 @@ void btrfs_print_leaf(const struct extent_buffer *l)
> print_uuid_item(l, btrfs_item_ptr_offset(l, i),
> btrfs_item_size(l, i));
> break;
> + case BTRFS_RAID_STRIPE_KEY:
> + print_raid_stripe_key(l, btrfs_item_size(l, i),
> + btrfs_item_ptr(l, i,
> + struct btrfs_stripe_extent));
> + break;
> }
> }
> }
>
> --
> 2.41.0
next prev parent reply other threads:[~2023-09-12 20:42 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 12:52 [PATCH v8 00/11] btrfs: introduce RAID stripe tree Johannes Thumshirn
2023-09-11 12:52 ` [PATCH v8 01/11] btrfs: add raid stripe tree definitions Johannes Thumshirn
2023-09-11 21:00 ` Damien Le Moal
2023-09-12 6:09 ` Johannes Thumshirn
2023-09-12 20:32 ` David Sterba
2023-09-13 6:02 ` Johannes Thumshirn
2023-09-13 14:49 ` David Sterba
2023-09-13 14:57 ` Johannes Thumshirn
2023-09-13 16:06 ` David Sterba
2023-09-11 12:52 ` [PATCH v8 02/11] btrfs: read raid-stripe-tree from disk Johannes Thumshirn
2023-09-14 9:27 ` Qu Wenruo
2023-09-14 9:33 ` Johannes Thumshirn
2023-09-11 12:52 ` [PATCH v8 03/11] btrfs: add support for inserting raid stripe extents Johannes Thumshirn
2023-09-13 16:50 ` David Sterba
2023-09-13 16:57 ` David Sterba
2023-09-14 9:25 ` Qu Wenruo
2023-09-14 9:51 ` Johannes Thumshirn
2023-09-14 10:06 ` Qu Wenruo
2023-09-14 15:35 ` Johannes Thumshirn
2023-09-11 12:52 ` [PATCH v8 04/11] btrfs: delete stripe extent on extent deletion Johannes Thumshirn
2023-09-11 12:52 ` [PATCH v8 05/11] btrfs: lookup physical address from stripe extent Johannes Thumshirn
2023-09-14 9:18 ` Qu Wenruo
2023-09-14 9:45 ` Johannes Thumshirn
2023-09-14 14:16 ` Johannes Thumshirn
2023-09-11 12:52 ` [PATCH v8 06/11] btrfs: implement RST version of scrub Johannes Thumshirn
2023-09-13 9:51 ` Qu Wenruo
2023-09-13 16:59 ` David Sterba
2023-09-11 12:52 ` [PATCH v8 07/11] btrfs: zoned: allow zoned RAID Johannes Thumshirn
2023-09-12 20:49 ` David Sterba
2023-09-13 5:41 ` Johannes Thumshirn
2023-09-13 14:52 ` David Sterba
2023-09-13 14:59 ` Johannes Thumshirn
2023-09-11 12:52 ` [PATCH v8 08/11] btrfs: add raid stripe tree pretty printer Johannes Thumshirn
2023-09-12 20:42 ` David Sterba [this message]
2023-09-13 5:34 ` Johannes Thumshirn
2023-09-11 12:52 ` [PATCH v8 09/11] btrfs: announce presence of raid-stripe-tree in sysfs Johannes Thumshirn
2023-09-11 12:52 ` [PATCH v8 10/11] btrfs: add trace events for RST Johannes Thumshirn
2023-09-12 20:46 ` David Sterba
2023-09-11 12:52 ` [PATCH v8 11/11] btrfs: add raid-stripe-tree to features enabled with debug 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=20230912204239.GF20408@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dlemoal@kernel.org \
--cc=dsterba@suse.com \
--cc=hch@lst.de \
--cc=johannes.thumshirn@wdc.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naohiro.aota@wdc.com \
--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
all inboxes | Powered by JetHome®