All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Chandan Babu R <chandan.babu@oracle.com>,
	Dave Chinner <david@fromorbit.com>,
	linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/3] xfs: move more logic into xfs_extent_busy_clear_one
Date: Fri, 5 Apr 2024 08:44:29 -0700	[thread overview]
Message-ID: <20240405154429.GZ6390@frogsfrogsfrogs> (raw)
In-Reply-To: <20240405060710.227096-2-hch@lst.de>

On Fri, Apr 05, 2024 at 08:07:08AM +0200, Christoph Hellwig wrote:
> Move the handling of discarded entries into xfs_extent_busy_clear_one
> to reuse the length check and tidy up the logic in the caller.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>

AFAICT, the return value of xfs_extent_busy_clear_one is whether
or not it actually changed the pagb_tree, right?  And if that return
value is true, then we want to wake up anyone who might be waiting on
busy extents to clear the pagb_tree, which is what the @wakeup logic
does, right?

If the answers are yes and yes, then:
Reviewed-by: Darrick J. Wong <djwong@kernel.org>

--D


> ---
>  fs/xfs/xfs_extent_busy.c | 23 ++++++++++++-----------
>  1 file changed, 12 insertions(+), 11 deletions(-)
> 
> diff --git a/fs/xfs/xfs_extent_busy.c b/fs/xfs/xfs_extent_busy.c
> index 56cfa1498571e3..6fbffa46e5e94b 100644
> --- a/fs/xfs/xfs_extent_busy.c
> +++ b/fs/xfs/xfs_extent_busy.c
> @@ -518,20 +518,26 @@ xfs_extent_busy_trim(
>  	goto out;
>  }
>  
> -STATIC void
> +static bool
>  xfs_extent_busy_clear_one(
> -	struct xfs_mount	*mp,
>  	struct xfs_perag	*pag,
> -	struct xfs_extent_busy	*busyp)
> +	struct xfs_extent_busy	*busyp,
> +	bool			do_discard)
>  {
>  	if (busyp->length) {
> -		trace_xfs_extent_busy_clear(mp, busyp->agno, busyp->bno,
> -						busyp->length);
> +		if (do_discard &&
> +		    !(busyp->flags & XFS_EXTENT_BUSY_SKIP_DISCARD)) {
> +			busyp->flags = XFS_EXTENT_BUSY_DISCARDED;
> +			return false;
> +		}
> +		trace_xfs_extent_busy_clear(pag->pag_mount, busyp->agno,
> +				busyp->bno, busyp->length);
>  		rb_erase(&busyp->rb_node, &pag->pagb_tree);
>  	}
>  
>  	list_del_init(&busyp->list);
>  	kfree(busyp);
> +	return true;
>  }
>  
>  static void
> @@ -575,13 +581,8 @@ xfs_extent_busy_clear(
>  			wakeup = false;
>  		}
>  
> -		if (do_discard && busyp->length &&
> -		    !(busyp->flags & XFS_EXTENT_BUSY_SKIP_DISCARD)) {
> -			busyp->flags = XFS_EXTENT_BUSY_DISCARDED;
> -		} else {
> -			xfs_extent_busy_clear_one(mp, pag, busyp);
> +		if (xfs_extent_busy_clear_one(pag, busyp, do_discard))
>  			wakeup = true;
> -		}
>  	}
>  
>  	if (pag)
> -- 
> 2.39.2
> 
> 

  reply	other threads:[~2024-04-05 15:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05  6:07 spring cleaning for xfs_extent_busy_clear Christoph Hellwig
2024-04-05  6:07 ` [PATCH 1/3] xfs: move more logic into xfs_extent_busy_clear_one Christoph Hellwig
2024-04-05 15:44   ` Darrick J. Wong [this message]
2024-04-05 16:40     ` Christoph Hellwig
2024-04-05  6:07 ` [PATCH 2/3] xfs: unwind xfs_extent_busy_clear Christoph Hellwig
2024-04-05 15:45   ` Darrick J. Wong
2024-04-05  6:07 ` [PATCH 3/3] xfs: remove the unused xfs_extent_busy_enomem trace event Christoph Hellwig
2024-04-05 15:31   ` Darrick J. Wong

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=20240405154429.GZ6390@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=chandan.babu@oracle.com \
    --cc=david@fromorbit.com \
    --cc=hch@lst.de \
    --cc=linux-xfs@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.