public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Gabriel Niebler <gniebler@suse.com>
Cc: linux-btrfs@vger.kernel.org, dsterba@suse.com
Subject: Re: [PATCH v3 0/14] btrfs: Introduce macro to iterate over slots
Date: Tue, 8 Mar 2022 15:27:31 +0100	[thread overview]
Message-ID: <20220308142731.GK12643@twin.jikos.cz> (raw)
In-Reply-To: <20220302164829.17524-1-gniebler@suse.com>

On Wed, Mar 02, 2022 at 05:48:15PM +0100, Gabriel Niebler wrote:
> There is a common pattern when searching for a key in btrfs:
> 
> * Call btrfs_search_slot to find the slot for the key
> * Enter an endless loop:
> 	* If the found slot is larger than the no. of items in the current leaf,
> 	  check the next leaf
> 	* If it's still not found in the next leaf, terminate the loop
> 	* Otherwise do something with the found key
> 	* Increment the current slot and continue
> 
> To reduce code duplication, we can replace this code pattern with an iterator
> macro, similar to the existing for_each_X macros found elsewhere in the kernel.
> This also makes the code easier to understand for newcomers by putting a name
> to the encapsulated functionality.
> 
> This patchset survived a complete fstest run.
> 
> Changes from v2:
>  * Rename btrfs_valid_slot to btrfs_get_next_valid_item (Nikolay)
>  * Fix comment formatting (David)
>  * Remove redundant parentheses and indentation in loop condition (David)
>  * Remove redundant iter_ret var and reuse ret instead (Nikolay)
>  * Make termination condition more consistent in btrfs_unlink_all_paths
>    (Nikolay)
>  * Improved patch organisation by splitting into one patch per function (David)
>  * Improve doc comment for btrfs_get_next_valid_item (Gabriel)
>  * Remove `out` label and assoc. gotos from id_create_dir (Gabriel)
>  * Initialise `ret` in process_all_refs and process_all_new_xattrs (Gabriel)
>  * Remove unneeded btrfs_item_key_to_cpu call from loop body in
>    btrfs_read_chunk_tree (Gabriel)

I still see some of the style issues not addressed in your version, I'll
point them out in the first example I find but it needs to be fixed in
all of them. Otherwise it looks good. As we're near the code freeze for
5.17 I'm not sure I could put it there so it's 5.18 at the latest.

      parent reply	other threads:[~2022-03-08 14:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-02 16:48 [PATCH v3 0/14] btrfs: Introduce macro to iterate over slots Gabriel Niebler
2022-03-02 16:48 ` [PATCH v3 01/14] btrfs: Introduce btrfs_for_each_slot iterator macro Gabriel Niebler
2022-03-08 14:31   ` David Sterba
2022-03-02 16:48 ` [PATCH v3 02/14] btrfs: Use btrfs_for_each_slot in find_first_block_group Gabriel Niebler
2022-03-02 16:48 ` [PATCH v3 03/14] btrfs: Use btrfs_for_each_slot in mark_block_group_to_copy Gabriel Niebler
2022-03-08 14:33   ` David Sterba
2022-03-02 16:48 ` [PATCH v3 04/14] btrfs: Use btrfs_for_each_slot in btrfs_search_dir_index_item Gabriel Niebler
2022-03-02 16:48 ` [PATCH v3 05/14] btrfs: Use btrfs_for_each_slot in btrfs_real_readdir Gabriel Niebler
2022-03-02 16:48 ` [PATCH v3 06/14] btrfs: Use btrfs_for_each_slot in did_create_dir Gabriel Niebler
2022-03-02 16:48 ` [PATCH v3 07/14] btrfs: Use btrfs_for_each_slot in can_rmdir Gabriel Niebler
2022-03-02 16:48 ` [PATCH v3 08/14] btrfs: Use btrfs_for_each_slot in is_ancestor Gabriel Niebler
2022-03-02 16:48 ` [PATCH v3 09/14] btrfs: Use btrfs_for_each_slot in process_all_refs Gabriel Niebler
2022-03-02 16:48 ` [PATCH v3 10/14] btrfs: Use btrfs_for_each_slot in process_all_new_xattrs Gabriel Niebler
2022-03-02 16:48 ` [PATCH v3 11/14] btrfs: Use btrfs_for_each_slot in process_all_extents Gabriel Niebler
2022-03-02 16:48 ` [PATCH v3 12/14] btrfs: Use btrfs_for_each_slot in btrfs_unlink_all_paths Gabriel Niebler
2022-03-08 15:29   ` Josef Bacik
2022-03-02 16:48 ` [PATCH v3 13/14] btrfs: Use btrfs_for_each_slot in btrfs_read_chunk_tree Gabriel Niebler
2022-03-02 16:48 ` [PATCH v3 14/14] btrfs: Use btrfs_for_each_slot in btrfs_listxattr Gabriel Niebler
2022-03-08 14:27 ` David Sterba [this message]

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=20220308142731.GK12643@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=dsterba@suse.com \
    --cc=gniebler@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