From: "Darrick J. Wong" <djwong@kernel.org>
To: John Garry <john.g.garry@oracle.com>
Cc: brauner@kernel.org, cem@kernel.org, dchinner@redhat.com,
hch@lst.de, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
ojaswin@linux.ibm.com, ritesh.list@gmail.com,
martin.petersen@oracle.com, tytso@mit.edu,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH v2 10/11] xfs: Update atomic write max size
Date: Mon, 24 Feb 2025 12:34:39 -0800 [thread overview]
Message-ID: <20250224203439.GK21808@frogsfrogsfrogs> (raw)
In-Reply-To: <20250213135619.1148432-11-john.g.garry@oracle.com>
On Thu, Feb 13, 2025 at 01:56:18PM +0000, John Garry wrote:
> Now that CoW-based atomic writes are supported, update the max size of an
> atomic write.
>
> For simplicity, limit at the max of what the mounted bdev can support in
> terms of atomic write limits. Maybe in future we will have a better way
> to advertise this optimised limit.
>
> In addition, the max atomic write size needs to be aligned to the agsize.
> Limit the size of atomic writes to the greatest power-of-two factor of the
> agsize so that allocations for an atomic write will always be aligned
> compatibly with the alignment requirements of the storage.
>
> For RT inode, just limit to 1x block, even though larger can be supported
> in future.
>
> Signed-off-by: John Garry <john.g.garry@oracle.com>
> ---
> fs/xfs/xfs_iops.c | 13 ++++++++++++-
> fs/xfs/xfs_iops.h | 1 -
> fs/xfs/xfs_mount.c | 28 ++++++++++++++++++++++++++++
> fs/xfs/xfs_mount.h | 1 +
> 4 files changed, 41 insertions(+), 2 deletions(-)
>
> diff --git a/fs/xfs/xfs_iops.c b/fs/xfs/xfs_iops.c
> index ea79fb246e33..d0a537696514 100644
> --- a/fs/xfs/xfs_iops.c
> +++ b/fs/xfs/xfs_iops.c
> @@ -606,12 +606,23 @@ xfs_get_atomic_write_attr(
> unsigned int *unit_min,
> unsigned int *unit_max)
> {
> + struct xfs_buftarg *target = xfs_inode_buftarg(ip);
> + struct xfs_mount *mp = ip->i_mount;
> +
> if (!xfs_inode_can_atomicwrite(ip)) {
> *unit_min = *unit_max = 0;
> return;
> }
>
> - *unit_min = *unit_max = ip->i_mount->m_sb.sb_blocksize;
> + *unit_min = ip->i_mount->m_sb.sb_blocksize;
> +
> + if (XFS_IS_REALTIME_INODE(ip)) {
> + /* For now, set limit at 1x block */
> + *unit_max = ip->i_mount->m_sb.sb_blocksize;
> + } else {
> + *unit_max = min_t(unsigned int, XFS_FSB_TO_B(mp, mp->awu_max),
> + target->bt_bdev_awu_max);
> + }
> }
>
> static void
> diff --git a/fs/xfs/xfs_iops.h b/fs/xfs/xfs_iops.h
> index ce7bdeb9a79c..d95a543f3ab0 100644
> --- a/fs/xfs/xfs_iops.h
> +++ b/fs/xfs/xfs_iops.h
> @@ -22,5 +22,4 @@ extern void xfs_diflags_to_iflags(struct xfs_inode *ip, bool init);
> void xfs_get_atomic_write_attr(struct xfs_inode *ip,
> unsigned int *unit_min, unsigned int *unit_max);
>
> -
No need to remove a blank line.
> #endif /* __XFS_IOPS_H__ */
> diff --git a/fs/xfs/xfs_mount.c b/fs/xfs/xfs_mount.c
> index 477c5262cf91..af3ed135be4d 100644
> --- a/fs/xfs/xfs_mount.c
> +++ b/fs/xfs/xfs_mount.c
> @@ -651,6 +651,32 @@ xfs_agbtree_compute_maxlevels(
> levels = max(levels, mp->m_rmap_maxlevels);
> mp->m_agbtree_maxlevels = max(levels, mp->m_refc_maxlevels);
> }
> +static inline void
> +xfs_compute_awu_max(
> + struct xfs_mount *mp)
> +{
> + xfs_agblock_t agsize = mp->m_sb.sb_agblocks;
> + xfs_agblock_t awu_max;
> +
> + if (!xfs_has_reflink(mp)) {
> + mp->awu_max = 1;
> + return;
> + }
> +
> + /*
> + * Find highest power-of-2 evenly divisible into agsize and which
> + * also fits into an unsigned int field.
> + */
> + awu_max = 1;
> + while (1) {
> + if (agsize % (awu_max * 2))
> + break;
> + if (XFS_FSB_TO_B(mp, awu_max * 2) > UINT_MAX)
> + break;
> + awu_max *= 2;
> + }
> + mp->awu_max = awu_max;
> +}
>
> /* Compute maximum possible height for realtime btree types for this fs. */
> static inline void
> @@ -736,6 +762,8 @@ xfs_mountfs(
> xfs_agbtree_compute_maxlevels(mp);
> xfs_rtbtree_compute_maxlevels(mp);
>
> + xfs_compute_awu_max(mp);
> +
> /*
> * Check if sb_agblocks is aligned at stripe boundary. If sb_agblocks
> * is NOT aligned turn off m_dalign since allocator alignment is within
> diff --git a/fs/xfs/xfs_mount.h b/fs/xfs/xfs_mount.h
> index fbed172d6770..34286c87ac4a 100644
> --- a/fs/xfs/xfs_mount.h
> +++ b/fs/xfs/xfs_mount.h
> @@ -198,6 +198,7 @@ typedef struct xfs_mount {
> bool m_fail_unmount;
> bool m_finobt_nores; /* no per-AG finobt resv. */
> bool m_update_sb; /* sb needs update in mount */
> + xfs_extlen_t awu_max; /* max atomic write */
Might want to clarify that this is for the *data* device.
/* max atomic write to datadev */
With those two things fixed,
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
>
> /*
> * Bitsets of per-fs metadata that have been checked and/or are sick.
> --
> 2.31.1
>
>
next prev parent reply other threads:[~2025-02-24 20:34 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 13:56 [PATCH v2 00/11] large atomic writes for xfs with CoW John Garry
2025-02-13 13:56 ` [PATCH v2 01/11] iomap: Rename IOMAP_ATOMIC -> IOMAP_ATOMIC_HW John Garry
2025-02-24 20:23 ` Darrick J. Wong
2025-02-13 13:56 ` [PATCH v2 02/11] xfs: Switch atomic write size check in xfs_file_write_iter() John Garry
2025-02-24 20:24 ` Darrick J. Wong
2025-02-13 13:56 ` [PATCH v2 03/11] xfs: Refactor xfs_reflink_end_cow_extent() John Garry
2025-02-24 20:26 ` Darrick J. Wong
2025-02-25 10:01 ` John Garry
2025-02-25 17:29 ` Darrick J. Wong
2025-02-13 13:56 ` [PATCH v2 04/11] iomap: Support CoW-based atomic writes John Garry
2025-02-24 19:59 ` Darrick J. Wong
2025-02-25 10:19 ` John Garry
2025-02-25 17:33 ` Darrick J. Wong
2025-02-13 13:56 ` [PATCH v2 05/11] iomap: Lift blocksize restriction on " John Garry
2025-02-13 13:56 ` [PATCH v2 06/11] xfs: Reflink CoW-based atomic write support John Garry
2025-02-24 20:32 ` Darrick J. Wong
2025-02-25 10:58 ` John Garry
2025-02-25 17:37 ` Darrick J. Wong
2025-02-25 18:02 ` John Garry
2025-02-13 13:56 ` [PATCH v2 07/11] xfs: iomap " John Garry
2025-02-24 20:13 ` Darrick J. Wong
2025-02-25 11:06 ` John Garry
2025-02-25 17:47 ` Darrick J. Wong
2025-02-25 18:07 ` John Garry
2025-02-13 13:56 ` [PATCH v2 08/11] xfs: Add xfs_file_dio_write_atomic() John Garry
2025-02-24 20:32 ` Darrick J. Wong
2025-02-13 13:56 ` [PATCH v2 09/11] xfs: Commit CoW-based atomic writes atomically John Garry
2025-02-24 20:20 ` Darrick J. Wong
2025-02-25 11:11 ` John Garry
2025-02-25 17:50 ` Darrick J. Wong
2025-02-25 18:07 ` John Garry
2025-02-13 13:56 ` [PATCH v2 10/11] xfs: Update atomic write max size John Garry
2025-02-24 20:34 ` Darrick J. Wong [this message]
2025-02-25 11:13 ` John Garry
2025-02-13 13:56 ` [PATCH v2 11/11] xfs: Allow block allocator to take an alignment hint John Garry
2025-02-24 20:37 ` Darrick J. Wong
2025-02-25 11:17 ` John Garry
2025-02-20 7:48 ` [PATCH v2 00/11] large atomic writes for xfs with CoW John Garry
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=20250224203439.GK21808@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=dchinner@redhat.com \
--cc=hch@lst.de \
--cc=john.g.garry@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
/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