public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 06/10] btrfs: relocation: Use wrapper to replace open-coded edge linking
Date: Tue, 3 Mar 2020 18:30:15 +0100	[thread overview]
Message-ID: <20200303173015.GL2902@twin.jikos.cz> (raw)
In-Reply-To: <20200302094553.58827-7-wqu@suse.com>

On Mon, Mar 02, 2020 at 05:45:49PM +0800, Qu Wenruo wrote:
> Since backref_edge is used to connect upper and lower backref nodes, and
> need to access both nodes, some code can look pretty nasty:
> 
> 		list_add_tail(&edge->list[LOWER], &cur->upper);
> 
> The above code will link @cur to the LOWER side of the edge, while both
> "LOWER" and "upper" words show up.
> This can sometimes be very confusing for reader to grasp.
> 
> This patch introduce a new wrapper, link_backref_edge(), to handle the
> linking behavior.
> Which also has extra ASSERT() to ensure caller won't pass wrong nodes
> in.
> 
> Also, this updates the comment of related lists of backref_node and
> backref_edge, to make it more clear that each list points to what.
> 
> Signed-off-by: Qu Wenruo <wqu@suse.com>
> ---
>  fs/btrfs/relocation.c | 53 ++++++++++++++++++++++++++++++-------------
>  1 file changed, 37 insertions(+), 16 deletions(-)
> 
> diff --git a/fs/btrfs/relocation.c b/fs/btrfs/relocation.c
> index 04416489d87a..c76849409c81 100644
> --- a/fs/btrfs/relocation.c
> +++ b/fs/btrfs/relocation.c
> @@ -91,10 +91,12 @@ struct backref_node {
>  	u64 owner;
>  	/* link to pending, changed or detached list */
>  	struct list_head list;
> -	/* list of upper level blocks reference this block */
> +
> +	/* List of upper level edges, which links this node to its parent(s) */
>  	struct list_head upper;
> -	/* list of child blocks in the cache */
> +	/* List of lower level edges, which links this node to its child(ren) */
>  	struct list_head lower;
> +
>  	/* NULL if this node is not tree root */
>  	struct btrfs_root *root;
>  	/* extent buffer got by COW the block */
> @@ -123,17 +125,26 @@ struct backref_node {
>  	unsigned int detached:1;
>  };
>  
> +#define LOWER	0
> +#define UPPER	1
> +#define RELOCATION_RESERVED_NODES	256
>  /*
> - * present a block pointer in the backref cache
> + * present an edge connecting upper and lower backref nodes.
>   */
>  struct backref_edge {
> +	/*
> +	 * list[LOWER] is linked to backref_node::upper of lower level node,
> +	 * and list[UPPER] is linked to backref_node::lower of upper level node.
> +	 *
> +	 * Also, build_backref_tree() uses list[UPPER] for pending edges, before
> +	 * linking list[UPPER] to its upper level nodes.
> +	 */
>  	struct list_head list[2];
> +
> +	/* Two related nodes */
>  	struct backref_node *node[2];
>  };
>  
> -#define LOWER	0
> -#define UPPER	1
> -#define RELOCATION_RESERVED_NODES	256
>  
>  struct backref_cache {
>  	/* red black tree of all backref nodes in the cache */
> @@ -332,6 +343,22 @@ static struct backref_edge *alloc_backref_edge(struct backref_cache *cache)
>  	return edge;
>  }
>  
> +#define		LINK_LOWER	(1 << 0)
> +#define		LINK_UPPER	(1 << 1)
> +static inline void link_backref_edge(struct backref_edge *edge,
> +				     struct backref_node *lower,
> +				     struct backref_node *upper,
> +				     int link_which)

Again not a static inline, but plain static function.

> +{
> +	ASSERT(upper && lower && upper->level == lower->level + 1);
> +	edge->node[LOWER] = lower;
> +	edge->node[UPPER] = upper;
> +	if (link_which & LINK_LOWER)
> +		list_add_tail(&edge->list[LOWER], &lower->upper);
> +	if (link_which & LINK_UPPER)
> +		list_add_tail(&edge->list[UPPER], &upper->lower);
> +}

  reply	other threads:[~2020-03-03 17:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-02  9:45 [PATCH v2 00/10] btrfs: relocation: Refactor build_backref_tree() Qu Wenruo
2020-03-02  9:45 ` [PATCH v2 01/10] btrfs: backref: Introduce the skeleton of btrfs_backref_iter Qu Wenruo
2020-03-03 17:19   ` David Sterba
2020-03-04  0:50     ` Qu Wenruo
2020-03-03 17:25   ` David Sterba
2020-03-04  0:52     ` Qu Wenruo
2020-03-04  7:41   ` Nikolay Borisov
2020-03-02  9:45 ` [PATCH v2 02/10] btrfs: backref: Implement btrfs_backref_iter_next() Qu Wenruo
2020-03-02  9:45 ` [PATCH v2 03/10] btrfs: relocation: Use btrfs_backref_iter infrastructure Qu Wenruo
2020-03-02  9:45 ` [PATCH v2 04/10] btrfs: relocation: Rename mark_block_processed() and __mark_block_processed() Qu Wenruo
2020-03-02 17:21   ` Nikolay Borisov
2020-03-02  9:45 ` [PATCH v2 05/10] btrfs: relocation: Refactor tree backref processing into its own function Qu Wenruo
2020-03-03 17:29   ` David Sterba
2020-03-04  1:00     ` Qu Wenruo
2020-03-04 12:23   ` Nikolay Borisov
2020-03-04 12:33     ` Qu Wenruo
2020-03-02  9:45 ` [PATCH v2 06/10] btrfs: relocation: Use wrapper to replace open-coded edge linking Qu Wenruo
2020-03-03 17:30   ` David Sterba [this message]
2020-03-04  1:02     ` Qu Wenruo
2020-03-04 13:02   ` Nikolay Borisov
2020-03-02  9:45 ` [PATCH v2 07/10] btrfs: relocation: Specify essential members for alloc_backref_node() Qu Wenruo
2020-03-04 13:06   ` Nikolay Borisov
2020-03-04 13:09     ` Qu Wenruo
2020-03-02  9:45 ` [PATCH v2 08/10] btrfs: relocation: Remove the open-coded goto loop for breadth-first search Qu Wenruo
2020-03-04 14:24   ` Nikolay Borisov
2020-03-05  0:40     ` Qu Wenruo
2020-03-05  8:17       ` Nikolay Borisov
2020-03-05  8:37         ` Qu Wenruo
2020-03-02  9:45 ` [PATCH v2 09/10] btrfs: relocation: Refactor the finishing part of upper linkage into finish_upper_links() Qu Wenruo
2020-03-02  9:45 ` [PATCH v2 10/10] btrfs: relocation: Refactor the useless nodes handling into its own function 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=20200303173015.GL2902@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --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