public inbox for linux-xfs@vger.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>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/5] xfs: use kfree_rcu_mightsleep to free the perag structures
Date: Thu, 29 Aug 2024 14:19:20 -0700	[thread overview]
Message-ID: <20240829211920.GK6224@frogsfrogsfrogs> (raw)
In-Reply-To: <20240829040848.1977061-2-hch@lst.de>

On Thu, Aug 29, 2024 at 07:08:37AM +0300, Christoph Hellwig wrote:
> Using the kfree_rcu_mightsleep is simpler and removes the need for a
> rcu_head in the perag structure.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>

Looks good to me!
Reviewed-by: Darrick J. Wong <djwong@kernel.org>

--D

> ---
>  fs/xfs/libxfs/xfs_ag.c | 12 +-----------
>  fs/xfs/libxfs/xfs_ag.h |  3 ---
>  2 files changed, 1 insertion(+), 14 deletions(-)
> 
> diff --git a/fs/xfs/libxfs/xfs_ag.c b/fs/xfs/libxfs/xfs_ag.c
> index 7e80732cb54708..4b5a39a83f7aed 100644
> --- a/fs/xfs/libxfs/xfs_ag.c
> +++ b/fs/xfs/libxfs/xfs_ag.c
> @@ -235,16 +235,6 @@ xfs_initialize_perag_data(
>  	return error;
>  }
>  
> -STATIC void
> -__xfs_free_perag(
> -	struct rcu_head	*head)
> -{
> -	struct xfs_perag *pag = container_of(head, struct xfs_perag, rcu_head);
> -
> -	ASSERT(!delayed_work_pending(&pag->pag_blockgc_work));
> -	kfree(pag);
> -}
> -
>  /*
>   * Free up the per-ag resources associated with the mount structure.
>   */
> @@ -270,7 +260,7 @@ xfs_free_perag(
>  		xfs_perag_rele(pag);
>  		XFS_IS_CORRUPT(pag->pag_mount,
>  				atomic_read(&pag->pag_active_ref) != 0);
> -		call_rcu(&pag->rcu_head, __xfs_free_perag);
> +		kfree_rcu_mightsleep(pag);
>  	}
>  }
>  
> diff --git a/fs/xfs/libxfs/xfs_ag.h b/fs/xfs/libxfs/xfs_ag.h
> index 35de09a2516c70..d62c266c0b44d5 100644
> --- a/fs/xfs/libxfs/xfs_ag.h
> +++ b/fs/xfs/libxfs/xfs_ag.h
> @@ -63,9 +63,6 @@ struct xfs_perag {
>  	/* Blocks reserved for the reverse mapping btree. */
>  	struct xfs_ag_resv	pag_rmapbt_resv;
>  
> -	/* for rcu-safe freeing */
> -	struct rcu_head	rcu_head;
> -
>  	/* Precalculated geometry info */
>  	xfs_agblock_t		block_count;
>  	xfs_agblock_t		min_block;
> -- 
> 2.43.0
> 
> 

  reply	other threads:[~2024-08-29 21:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-29  4:08 convert XFS perag lookup to xarrays v3 Christoph Hellwig
2024-08-29  4:08 ` [PATCH 1/5] xfs: use kfree_rcu_mightsleep to free the perag structures Christoph Hellwig
2024-08-29 21:19   ` Darrick J. Wong [this message]
2024-08-29  4:08 ` [PATCH 2/5] xfs: move the tagged perag lookup helpers to xfs_icache.c Christoph Hellwig
2024-08-29 21:26   ` Darrick J. Wong
2024-08-29  4:08 ` [PATCH 3/5] xfs: simplify tagged perag iteration Christoph Hellwig
2024-08-29 21:24   ` Darrick J. Wong
2024-08-29  4:08 ` [PATCH 4/5] xfs: convert perag lookup to xarray Christoph Hellwig
2024-08-29  4:08 ` [PATCH 5/5] xfs: use xas_for_each_marked in xfs_reclaim_inodes_count Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2024-08-21  6:38 convert XFS perag lookup to xarrays v2 Christoph Hellwig
2024-08-21  6:38 ` [PATCH 1/5] xfs: use kfree_rcu_mightsleep to free the perag structures Christoph Hellwig
2024-08-21 16:19   ` Darrick J. Wong
2024-08-22  3:42     ` Christoph Hellwig

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=20240829211920.GK6224@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=chandan.babu@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox