public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chandan Babu R <chandanrlinux@gmail.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: avoid shared rmap operations for attr fork extents
Date: Thu, 24 Sep 2020 10:14:13 +0530	[thread overview]
Message-ID: <20014204.GQ1xNvM1QS@garuda> (raw)
In-Reply-To: <20200923182340.GV7955@magnolia>

On Wednesday 23 September 2020 11:53:40 PM IST Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
> 
> During code review, I noticed that the rmap code uses the (slower)
> shared mappings rmap functions for any extent of a reflinked file, even
> if those extents are for the attr fork, which doesn't support sharing.
> We can speed up rmap a tiny bit by optimizing out this case.
> 
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>

Looks good to me.

Reviewed-by: Chandan Babu R <chandanrlinux@gmail.com>

> ---
>  fs/xfs/libxfs/xfs_rmap.c |   27 ++++++++++++++++++---------
>  1 file changed, 18 insertions(+), 9 deletions(-)
> 
> diff --git a/fs/xfs/libxfs/xfs_rmap.c b/fs/xfs/libxfs/xfs_rmap.c
> index 27c39268c31f..340c83f76c80 100644
> --- a/fs/xfs/libxfs/xfs_rmap.c
> +++ b/fs/xfs/libxfs/xfs_rmap.c
> @@ -2505,12 +2505,15 @@ xfs_rmap_map_extent(
>  	int			whichfork,
>  	struct xfs_bmbt_irec	*PREV)
>  {
> +	enum xfs_rmap_intent_type type = XFS_RMAP_MAP;
> +
>  	if (!xfs_rmap_update_is_needed(tp->t_mountp, whichfork))
>  		return;
>  
> -	__xfs_rmap_add(tp, xfs_is_reflink_inode(ip) ?
> -			XFS_RMAP_MAP_SHARED : XFS_RMAP_MAP, ip->i_ino,
> -			whichfork, PREV);
> +	if (whichfork != XFS_ATTR_FORK && xfs_is_reflink_inode(ip))
> +		type = XFS_RMAP_MAP_SHARED;
> +
> +	__xfs_rmap_add(tp, type, ip->i_ino, whichfork, PREV);
>  }
>  
>  /* Unmap an extent out of a file. */
> @@ -2521,12 +2524,15 @@ xfs_rmap_unmap_extent(
>  	int			whichfork,
>  	struct xfs_bmbt_irec	*PREV)
>  {
> +	enum xfs_rmap_intent_type type = XFS_RMAP_UNMAP;
> +
>  	if (!xfs_rmap_update_is_needed(tp->t_mountp, whichfork))
>  		return;
>  
> -	__xfs_rmap_add(tp, xfs_is_reflink_inode(ip) ?
> -			XFS_RMAP_UNMAP_SHARED : XFS_RMAP_UNMAP, ip->i_ino,
> -			whichfork, PREV);
> +	if (whichfork != XFS_ATTR_FORK && xfs_is_reflink_inode(ip))
> +		type = XFS_RMAP_UNMAP_SHARED;
> +
> +	__xfs_rmap_add(tp, type, ip->i_ino, whichfork, PREV);
>  }
>  
>  /*
> @@ -2543,12 +2549,15 @@ xfs_rmap_convert_extent(
>  	int			whichfork,
>  	struct xfs_bmbt_irec	*PREV)
>  {
> +	enum xfs_rmap_intent_type type = XFS_RMAP_CONVERT;
> +
>  	if (!xfs_rmap_update_is_needed(mp, whichfork))
>  		return;
>  
> -	__xfs_rmap_add(tp, xfs_is_reflink_inode(ip) ?
> -			XFS_RMAP_CONVERT_SHARED : XFS_RMAP_CONVERT, ip->i_ino,
> -			whichfork, PREV);
> +	if (whichfork != XFS_ATTR_FORK && xfs_is_reflink_inode(ip))
> +		type = XFS_RMAP_CONVERT_SHARED;
> +
> +	__xfs_rmap_add(tp, type, ip->i_ino, whichfork, PREV);
>  }
>  
>  /* Schedule the creation of an rmap for non-file data. */
> 


-- 
chandan




  reply	other threads:[~2020-09-24  4:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23 18:23 [PATCH] xfs: avoid shared rmap operations for attr fork extents Darrick J. Wong
2020-09-24  4:44 ` Chandan Babu R [this message]
2020-09-24  5:44 ` 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=20014204.GQ1xNvM1QS@garuda \
    --to=chandanrlinux@gmail.com \
    --cc=darrick.wong@oracle.com \
    --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