All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: fdmanana@kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 01/12] btrfs: balance btree dirty pages and delayed items after a rename
Date: Wed, 1 Jun 2022 04:43:40 +0530	[thread overview]
Message-ID: <a2ee10fd-f2ea-8407-ed11-965117fcc224@oracle.com> (raw)
In-Reply-To: <06a51882e0ce06794248a10f5c1c70b987dab62f.1654009356.git.fdmanana@suse.com>

On 5/31/22 20:36, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
> 
> A rename operation modifies a subvolume's btree, to remove the old dir
> item, add the new dir item, remove an inode ref and add a new inode ref.
> It can also create the delayed inode for the inodes involved in the
> operation, and it creates two delayed dir index items, one to delete
> the old name and another one to add the new name.
> 
> However we are neither balancing the btree dirty pages nor the delayed
> items after a rename, which can result in accumulation of too many
> btree dirty pages and delayed items, specially if a task is doing a
> series of rename operations (for example it can happen for package
> installations/upgrades through the zypper tool).
> 
> So just call btrfs_btree_balance_dirty() after a rename, just like we
> do for every other system call that results on modifying a btree and
> adding delayed items.
> 


LGTM

Reviewed-by: Anand Jain <anand.jain@oracle.com>


> Signed-off-by: Filipe Manana <fdmanana@suse.com>
> ---
>   fs/btrfs/inode.c | 14 ++++++++++----
>   1 file changed, 10 insertions(+), 4 deletions(-)
> 
> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
> index ba913ea6f4d1..06d5bfa84d38 100644
> --- a/fs/btrfs/inode.c
> +++ b/fs/btrfs/inode.c
> @@ -9546,15 +9546,21 @@ static int btrfs_rename2(struct user_namespace *mnt_userns, struct inode *old_di
>   			 struct dentry *old_dentry, struct inode *new_dir,
>   			 struct dentry *new_dentry, unsigned int flags)
>   {
> +	int ret;
> +
>   	if (flags & ~(RENAME_NOREPLACE | RENAME_EXCHANGE | RENAME_WHITEOUT))
>   		return -EINVAL;
>   
>   	if (flags & RENAME_EXCHANGE)
> -		return btrfs_rename_exchange(old_dir, old_dentry, new_dir,
> -					  new_dentry);
> +		ret = btrfs_rename_exchange(old_dir, old_dentry, new_dir,
> +					    new_dentry);
> +	else
> +		ret = btrfs_rename(mnt_userns, old_dir, old_dentry, new_dir,
> +				   new_dentry, flags);
>   
> -	return btrfs_rename(mnt_userns, old_dir, old_dentry, new_dir,
> -			    new_dentry, flags);
> +	btrfs_btree_balance_dirty(BTRFS_I(new_dir)->root->fs_info);
> +
> +	return ret;
>   }
>   
>   struct btrfs_delalloc_work {


  parent reply	other threads:[~2022-05-31 23:14 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 15:06 [PATCH 00/12] btrfs: some improvements and cleanups around delayed items fdmanana
2022-05-31 15:06 ` [PATCH 01/12] btrfs: balance btree dirty pages and delayed items after a rename fdmanana
2022-05-31 15:16   ` Nikolay Borisov
2022-05-31 23:13   ` Anand Jain [this message]
2022-05-31 15:06 ` [PATCH 02/12] btrfs: free the path earlier when creating a new inode fdmanana
2022-05-31 15:21   ` Nikolay Borisov
2022-05-31 23:22   ` Anand Jain
2022-06-01  9:34     ` Filipe Manana
2022-06-01 11:11       ` Anand Jain
2022-06-01 11:51         ` David Sterba
2022-05-31 15:06 ` [PATCH 03/12] btrfs: balance btree dirty pages and delayed items after clone and dedupe fdmanana
2022-06-01  0:54   ` Anand Jain
2022-05-31 15:06 ` [PATCH 04/12] btrfs: add assertions when deleting batches of delayed items fdmanana
2022-06-01  1:34   ` Anand Jain
2022-05-31 15:06 ` [PATCH 05/12] btrfs: deal with deletion errors when deleting " fdmanana
2022-06-01  1:44   ` Anand Jain
2022-05-31 15:06 ` [PATCH 06/12] btrfs: refactor the delayed item deletion entry point fdmanana
2022-05-31 15:06 ` [PATCH 07/12] btrfs: improve batch deletion of delayed dir index items fdmanana
2022-06-02  8:24   ` Nikolay Borisov
2022-06-02  8:55     ` Filipe Manana
2022-05-31 15:06 ` [PATCH 08/12] btrfs: assert that delayed item is a dir index item when adding it fdmanana
2022-05-31 15:06 ` [PATCH 09/12] btrfs: improve batch insertion of delayed dir index items fdmanana
2022-05-31 15:06 ` [PATCH 10/12] btrfs: do not BUG_ON() on failure to reserve metadata for delayed item fdmanana
2022-05-31 15:06 ` [PATCH 11/12] btrfs: set delayed item type when initializing it fdmanana
2022-05-31 15:06 ` [PATCH 12/12] btrfs: reduce amount of reserved metadata for delayed item insertion fdmanana
2022-06-08 15:23   ` [btrfs] 62bd8124e2: WARNING:at_fs/btrfs/block-rsv.c:#btrfs_release_global_block_rsv[btrfs] kernel test robot
2022-06-08 15:23     ` kernel test robot
2022-06-09  9:46     ` Filipe Manana
2022-06-09  9:46       ` Filipe Manana
2022-06-10  1:26       ` Oliver Sang
2022-06-10  1:26         ` Oliver Sang
2022-06-12 14:36         ` Oliver Sang
2022-06-12 14:36           ` Oliver Sang
2022-06-13 10:50           ` Filipe Manana
2022-06-13 10:50             ` Filipe Manana
2022-06-16  2:42             ` Oliver Sang
2022-06-16  2:42               ` Oliver Sang
2022-06-17 10:32               ` Filipe Manana
2022-06-17 10:32                 ` Filipe Manana
2022-06-01 18:35 ` [PATCH 00/12] btrfs: some improvements and cleanups around delayed items David Sterba
2022-06-02  9:34 ` Nikolay Borisov

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=a2ee10fd-f2ea-8407-ed11-965117fcc224@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=fdmanana@kernel.org \
    --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 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.