From: Dave Chinner <david@fromorbit.com>
To: Catherine Hoang <catherine.hoang@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH v4] xfs: allow read IO and FICLONE to run concurrently
Date: Wed, 18 Oct 2023 10:59:10 +1100 [thread overview]
Message-ID: <ZS8fztyv43GKNdZR@dread.disaster.area> (raw)
In-Reply-To: <20231017201208.18127-1-catherine.hoang@oracle.com>
On Tue, Oct 17, 2023 at 01:12:08PM -0700, Catherine Hoang wrote:
> One of our VM cluster management products needs to snapshot KVM image
> files so that they can be restored in case of failure. Snapshotting is
> done by redirecting VM disk writes to a sidecar file and using reflink
> on the disk image, specifically the FICLONE ioctl as used by
> "cp --reflink". Reflink locks the source and destination files while it
> operates, which means that reads from the main vm disk image are blocked,
> causing the vm to stall. When an image file is heavily fragmented, the
> copy process could take several minutes. Some of the vm image files have
> 50-100 million extent records, and duplicating that much metadata locks
> the file for 30 minutes or more. Having activities suspended for such
> a long time in a cluster node could result in node eviction.
>
> Clone operations and read IO do not change any data in the source file,
> so they should be able to run concurrently. Demote the exclusive locks
> taken by FICLONE to shared locks to allow reads while cloning. While a
> clone is in progress, writes will take the IOLOCK_EXCL, so they block
> until the clone completes.
>
> Link: https://lore.kernel.org/linux-xfs/8911B94D-DD29-4D6E-B5BC-32EAF1866245@oracle.com/
> Signed-off-by: Catherine Hoang <catherine.hoang@oracle.com>
> ---
> fs/xfs/xfs_file.c | 67 +++++++++++++++++++++++++++++++++++---------
> fs/xfs/xfs_inode.c | 17 +++++++++++
> fs/xfs/xfs_inode.h | 9 ++++++
> fs/xfs/xfs_reflink.c | 4 +++
> 4 files changed, 84 insertions(+), 13 deletions(-)
All looks OK - one minor nit below.
Reviewed-by: Dave Chinner <dchinner@redhat.com>
> diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
> index 203700278ddb..3b9500e18f90 100644
> --- a/fs/xfs/xfs_file.c
> +++ b/fs/xfs/xfs_file.c
> @@ -214,6 +214,47 @@ xfs_ilock_iocb(
> return 0;
> }
>
> +static int
> +xfs_ilock_iocb_for_write(
> + struct kiocb *iocb,
> + unsigned int *lock_mode)
> +{
> + ssize_t ret;
> + struct xfs_inode *ip = XFS_I(file_inode(iocb->ki_filp));
> +
> + ret = xfs_ilock_iocb(iocb, *lock_mode);
> + if (ret)
> + return ret;
> +
> + if (*lock_mode == XFS_IOLOCK_EXCL)
> + return 0;
> + if (!xfs_iflags_test(ip, XFS_IREMAPPING))
> + return 0;
> +
> + xfs_iunlock(ip, *lock_mode);
> + *lock_mode = XFS_IOLOCK_EXCL;
> + ret = xfs_ilock_iocb(iocb, *lock_mode);
> + if (ret)
> + return ret;
> +
> + return 0;
This last bit could simply be:
xfs_iunlock(ip, *lock_mode);
*lock_mode = XFS_IOLOCK_EXCL;
return xfs_ilock_iocb(iocb, *lock_mode);
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2023-10-17 23:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 20:12 [PATCH v4] xfs: allow read IO and FICLONE to run concurrently Catherine Hoang
2023-10-17 22:59 ` Darrick J. Wong
2023-10-17 23:59 ` Dave Chinner [this message]
2023-10-23 6:42 ` Chandan Babu R
2023-10-18 6:08 ` Christoph Hellwig
2023-10-19 20:04 ` Darrick J. Wong
2023-10-20 6:06 ` Christoph Hellwig
2023-10-20 15:34 ` Darrick J. Wong
2023-10-22 22:42 ` Dave Chinner
2023-10-23 15:40 ` 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=ZS8fztyv43GKNdZR@dread.disaster.area \
--to=david@fromorbit.com \
--cc=catherine.hoang@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