From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 08/10] btrfs: simplify data stripe calculation helpers
Date: Mon, 26 Jul 2021 20:38:16 +0800 [thread overview]
Message-ID: <41a6c967-1f34-b48a-c24c-14cf226a5c67@gmx.com> (raw)
In-Reply-To: <6e7fd9d9fe39f547eae063dac6e230f155980ba0.1627300614.git.dsterba@suse.com>
On 2021/7/26 下午8:15, David Sterba wrote:
> There are two helpers doing the same calculations based on nparity and
> ncopies. calc_data_stripes can be simplified into one expression, so far
> we don't have profile with both copies and parity, so there's no
> effective change. calc_stripe_length should reuse the helper and not
> repeat the same calculation.
>
> Signed-off-by: David Sterba <dsterba@suse.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Just one nitpick inlined below.
> ---
> fs/btrfs/volumes.c | 15 ++-------------
> 1 file changed, 2 insertions(+), 13 deletions(-)
>
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index d98e29556d79..78dd013d0ee3 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -3567,10 +3567,7 @@ static u64 calc_data_stripes(u64 type, int num_stripes)
> const int ncopies = btrfs_raid_array[index].ncopies;
> const int nparity = btrfs_raid_array[index].nparity;
>
> - if (nparity)
> - return num_stripes - nparity;
> - else
> - return num_stripes / ncopies;
I would prefer an ASSERT() here to be extra sure.
But it's my personal taste (and love for tons of ASSERT()).
Thanks,
Qu
> + return (num_stripes - nparity) / ncopies;
> }
>
> /* [pstart, pend) */
> @@ -6878,15 +6875,7 @@ static void btrfs_report_missing_device(struct btrfs_fs_info *fs_info,
>
> static u64 calc_stripe_length(u64 type, u64 chunk_len, int num_stripes)
> {
> - int index = btrfs_bg_flags_to_raid_index(type);
> - int ncopies = btrfs_raid_array[index].ncopies;
> - const int nparity = btrfs_raid_array[index].nparity;
> - int data_stripes;
> -
> - if (nparity)
> - data_stripes = num_stripes - nparity;
> - else
> - data_stripes = num_stripes / ncopies;
> + const int data_stripes = calc_data_stripes(type, num_stripes);
>
> return div_u64(chunk_len, data_stripes);
> }
>
next prev parent reply other threads:[~2021-07-26 12:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 12:15 [PATCH 00/10] Misc small cleanups David Sterba
2021-07-26 12:15 ` [PATCH 01/10] btrfs: switch uptodate to bool in btrfs_writepage_endio_finish_ordered David Sterba
2021-07-26 12:23 ` Qu Wenruo
2021-07-26 12:15 ` [PATCH 02/10] btrfs: remove uptodate parameter from btrfs_dec_test_first_ordered_pending David Sterba
2021-07-26 12:24 ` Qu Wenruo
2021-07-26 12:15 ` [PATCH 03/10] btrfs: make btrfs_next_leaf static inline David Sterba
2021-07-26 12:25 ` Qu Wenruo
2021-07-26 12:15 ` [PATCH 04/10] btrfs: tree-checker: use table values for stripe checks David Sterba
2021-07-26 12:29 ` Qu Wenruo
2021-07-26 14:47 ` David Sterba
2021-07-26 12:15 ` [PATCH 05/10] btrfs: tree-checker: add missing stripe checks for raid1c3/4 profiles David Sterba
2021-07-26 12:29 ` Qu Wenruo
2021-07-26 12:15 ` [PATCH 06/10] btrfs: uninline btrfs_bg_flags_to_raid_index David Sterba
2021-07-26 12:34 ` Qu Wenruo
2021-07-26 15:06 ` David Sterba
2021-07-26 12:15 ` [PATCH 07/10] btrfs: merge alloc_device helpers David Sterba
2021-07-26 12:35 ` Qu Wenruo
2021-07-26 12:15 ` [PATCH 08/10] btrfs: simplify data stripe calculation helpers David Sterba
2021-07-26 12:38 ` Qu Wenruo [this message]
2021-07-26 15:06 ` David Sterba
2021-07-26 22:23 ` Qu Wenruo
2021-07-27 8:39 ` David Sterba
2021-07-27 9:32 ` Qu Wenruo
2021-07-26 12:15 ` [PATCH 09/10] btrfs: constify and cleanup variables comparators David Sterba
2021-07-26 12:15 ` [PATCH 10/10] btrfs: add and use simple page/bio to inode/fs_info helpers David Sterba
2021-07-26 12:41 ` Qu Wenruo
2021-07-26 15:09 ` David Sterba
2021-07-26 22:26 ` Qu Wenruo
2021-07-27 8:45 ` David Sterba
2021-07-27 9:42 ` Qu Wenruo
2021-07-27 14:44 ` David Sterba
2021-07-27 15:03 ` [PATCH v2 " David Sterba
2021-07-28 0:12 ` Qu Wenruo
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=41a6c967-1f34-b48a-c24c-14cf226a5c67@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dsterba@suse.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).