All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: fdmanana@kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/8] btrfs: add a btrfs_chunk_map structure and preparatory cleanups
Date: Tue, 21 Nov 2023 09:12:44 -0500	[thread overview]
Message-ID: <20231121141244.GA1667963@perftesting> (raw)
In-Reply-To: <cover.1700573313.git.fdmanana@suse.com>

On Tue, Nov 21, 2023 at 01:38:31PM +0000, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
> 
> The following are some cleanups and introducing a dedicated data structure
> for representing chunk maps, in order to make code simpler and use less
> memory - this is achieved in patch 7/8. This patchset is also preparatory
> work for some upcoming changes to extent maps.
> 
> Filipe Manana (8):
>   btrfs: fix off-by-one when checking chunk map includes logical address
>   btrfs: make error messages more clear when getting a chunk map
>   btrfs: mark sanity checks when getting chunk map as unlikely
>   btrfs: split assert into two different asserts when removing block group
>   btrfs: unexport extent_map_block_end()
>   btrfs: use btrfs_next_item() at scrub.c:find_first_extent_item()
>   btrfs: use a dedicated data structure for chunk maps
>   btrfs: remove stripe size local variable from insert_dev_extents()
> 

Reviewed-by: Josef Bacik <josef@toxicpanda.com>

Thanks,

Josef

  parent reply	other threads:[~2023-11-21 14:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21 13:38 [PATCH 0/8] btrfs: add a btrfs_chunk_map structure and preparatory cleanups fdmanana
2023-11-21 13:38 ` [PATCH 1/8] btrfs: fix off-by-one when checking chunk map includes logical address fdmanana
2023-11-21 13:38 ` [PATCH 2/8] btrfs: make error messages more clear when getting a chunk map fdmanana
2023-11-21 13:38 ` [PATCH 3/8] btrfs: mark sanity checks when getting chunk map as unlikely fdmanana
2023-11-21 13:38 ` [PATCH 4/8] btrfs: split assert into two different asserts when removing block group fdmanana
2023-11-21 13:38 ` [PATCH 5/8] btrfs: unexport extent_map_block_end() fdmanana
2023-11-21 13:38 ` [PATCH 6/8] btrfs: use btrfs_next_item() at scrub.c:find_first_extent_item() fdmanana
2023-11-21 13:38 ` [PATCH 7/8] btrfs: use a dedicated data structure for chunk maps fdmanana
2023-11-21 15:19   ` David Sterba
2023-11-21 16:50     ` Filipe Manana
2023-11-21 18:08       ` David Sterba
2023-11-21 18:23   ` David Sterba
2023-11-22 11:32     ` Filipe Manana
2023-11-22 14:16       ` David Sterba
2023-11-21 21:25   ` kernel test robot
2023-11-22  0:53   ` kernel test robot
2023-11-22  0:55   ` kernel test robot
2023-11-21 13:38 ` [PATCH 8/8] btrfs: remove stripe size local variable from insert_dev_extents() fdmanana
2023-11-21 14:12 ` Josef Bacik [this message]
2023-11-21 21:03 ` [PATCH 0/8] btrfs: add a btrfs_chunk_map structure and preparatory cleanups 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=20231121141244.GA1667963@perftesting \
    --to=josef@toxicpanda.com \
    --cc=fdmanana@kernel.org \
    --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 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.