From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Carlos Maiolino <cem@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christian Brauner <brauner@kernel.org>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 05/21] xfs: introduce XFS_BLI_PREALLOC
Date: Thu, 24 Sep 2026 14:49:39 -0700 [thread overview]
Message-ID: <20260924214939.GG2705364@frogsfrogsfrogs> (raw)
In-Reply-To: <20260924100032.2733101-6-hch@lst.de>
On Thu, Sep 24, 2026 at 11:59:37AM +0200, Christoph Hellwig wrote:
> Add a flag so that the shadow CIL buffer for a buffer log item is always
> sizes to the maximum to prevent reallocations. This will be used for the
sized
> RT checksum item, where we know that we are going to fill it up very soon,
> and (almost) sequentially, so there is no point in doing a constant
> realloc cycle when more data is added to it.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> fs/xfs/libxfs/xfs_trans_resv.c | 2 +-
> fs/xfs/libxfs/xfs_trans_resv.h | 1 +
> fs/xfs/xfs_buf_item.c | 10 ++++++++++
> fs/xfs/xfs_buf_item.h | 4 +++-
> 4 files changed, 15 insertions(+), 2 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_trans_resv.c b/fs/xfs/libxfs/xfs_trans_resv.c
> index 3151e97ca8ff..5382ece51812 100644
> --- a/fs/xfs/libxfs/xfs_trans_resv.c
> +++ b/fs/xfs/libxfs/xfs_trans_resv.c
> @@ -53,7 +53,7 @@ xfs_buf_log_overhead(void)
> * will be changed in a transaction. size is used to tell how many
> * bytes should be reserved per item.
> */
> -STATIC uint
> +uint
> xfs_calc_buf_res(
> uint nbufs,
> uint size)
> diff --git a/fs/xfs/libxfs/xfs_trans_resv.h b/fs/xfs/libxfs/xfs_trans_resv.h
> index 336279e0fc61..1804e821f382 100644
> --- a/fs/xfs/libxfs/xfs_trans_resv.h
> +++ b/fs/xfs/libxfs/xfs_trans_resv.h
> @@ -96,6 +96,7 @@ struct xfs_trans_resv {
> #define XFS_ITRUNCATE_LOG_COUNT_REFLINK 8
> #define XFS_WRITE_LOG_COUNT_REFLINK 8
>
> +uint xfs_calc_buf_res(uint nbufs, uint size);
> void xfs_trans_resv_calc(struct xfs_mount *mp, struct xfs_trans_resv *resp);
> uint xfs_allocfree_block_count(struct xfs_mount *mp, uint num_ops);
>
> diff --git a/fs/xfs/xfs_buf_item.c b/fs/xfs/xfs_buf_item.c
> index 1a4ef34af8d5..644c3fb18310 100644
> --- a/fs/xfs/xfs_buf_item.c
> +++ b/fs/xfs/xfs_buf_item.c
> @@ -252,6 +252,16 @@ xfs_buf_item_size(
> offset += BBTOB(bp->b_maps[i].bm_len);
> }
>
> + /*
> + * For buffers with the prealloc flag, always size the allocation size
> + * to the maximum as per the log reservation. This avoids constant
> + * realloc cycles for buffers that are filled sequentially in rapid
> + * pace. Note that the nvecs calaculation is kept from the regular
calculation
> + * look as the buffer item formatting expects it.
"...is kept from the regular look as the buffer item formatting expects
it" ?
I don't understand that. Is the nvecs calculation kept as the buffer
item formatting code expects it, even though we're allocating more
shadow buffer space?
--D
> + */
> + if (bip->bli_flags & XFS_BLI_PREALLOC)
> + *nbytes = xfs_calc_buf_res(bip->bli_format_count, bp->b_length);
> +
> /*
> * Round up the buffer size required to minimise the number of memory
> * allocations that need to be done as this item grows when relogged by
> diff --git a/fs/xfs/xfs_buf_item.h b/fs/xfs/xfs_buf_item.h
> index 3159325dd17b..ddc8ecc4683e 100644
> --- a/fs/xfs/xfs_buf_item.h
> +++ b/fs/xfs/xfs_buf_item.h
> @@ -20,6 +20,7 @@ struct xfs_mount;
> #define XFS_BLI_STALE_INODE (1u << 5)
> #define XFS_BLI_INODE_BUF (1u << 6)
> #define XFS_BLI_ORDERED (1u << 7)
> +#define XFS_BLI_PREALLOC (1u << 8)
>
> #define XFS_BLI_FLAGS \
> { XFS_BLI_HOLD, "HOLD" }, \
> @@ -29,7 +30,8 @@ struct xfs_mount;
> { XFS_BLI_INODE_ALLOC_BUF, "INODE_ALLOC" }, \
> { XFS_BLI_STALE_INODE, "STALE_INODE" }, \
> { XFS_BLI_INODE_BUF, "INODE_BUF" }, \
> - { XFS_BLI_ORDERED, "ORDERED" }
> + { XFS_BLI_ORDERED, "ORDERED" }, \
> + { XFS_BLI_PREALLOC, "PREALLOC" }
>
> /*
> * This is the in core log item structure used to track information
> --
> 2.53.0
>
>
next prev parent reply other threads:[~2026-09-24 21:49 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 9:59 support for RT data checksums Christoph Hellwig
2026-09-24 9:59 ` [PATCH 01/21] block: export fs_bio_integrity_verify Christoph Hellwig
2026-09-24 20:29 ` Darrick J. Wong
2026-09-24 9:59 ` [PATCH 02/21] iomap: add support for data checksumming Christoph Hellwig
2026-09-24 21:39 ` Darrick J. Wong
2026-09-25 5:53 ` Christoph Hellwig
2026-09-24 9:59 ` [PATCH 03/21] xfs: add a xfs_buf_read_async buffer cache API Christoph Hellwig
2026-09-24 21:43 ` Darrick J. Wong
2026-09-25 5:54 ` Christoph Hellwig
2026-09-24 9:59 ` [PATCH 04/21] xfs: add xfs_daddr_to_rgno and xfs_daddr_to_rgbno helpers Christoph Hellwig
2026-09-24 21:44 ` Darrick J. Wong
2026-09-24 9:59 ` [PATCH 05/21] xfs: introduce XFS_BLI_PREALLOC Christoph Hellwig
2026-09-24 21:49 ` Darrick J. Wong [this message]
2026-09-25 5:57 ` Christoph Hellwig
2026-10-08 11:46 ` Anuj gupta
2026-09-24 9:59 ` [PATCH 06/21] xfs: prepare xfs_rtfile_initialize_blocks for larger than FSB blocks Christoph Hellwig
2026-09-24 22:03 ` Darrick J. Wong
2026-09-25 5:58 ` Christoph Hellwig
2026-09-24 9:59 ` [PATCH 07/21] xfs: relase zi_open_zones_lock over xfs_open_zone_put on unmount Christoph Hellwig
2026-09-24 9:59 ` [PATCH 08/21] xfs: define the RT data checksum on-disk format Christoph Hellwig
2026-09-24 22:13 ` Darrick J. Wong
2026-09-25 0:04 ` Eric Biggers
2026-09-25 6:01 ` Christoph Hellwig
2026-09-24 9:59 ` [PATCH 09/21] xfs: add support for per-RTG csum files Christoph Hellwig
2026-09-24 22:24 ` Darrick J. Wong
2026-09-25 6:10 ` Christoph Hellwig
2026-09-24 9:59 ` [PATCH 10/21] xfs: calculate the log reservation for logging data checksum buffers Christoph Hellwig
2026-09-24 22:30 ` Darrick J. Wong
2026-09-25 6:12 ` Christoph Hellwig
2026-09-24 9:59 ` [PATCH 11/21] xfs: core RT data checksum support Christoph Hellwig
2026-09-25 23:20 ` Darrick J. Wong
2026-09-26 6:13 ` Christoph Hellwig
2026-09-24 9:59 ` [PATCH 12/21] xfs: data checksums require stable writes Christoph Hellwig
2026-09-25 23:21 ` Darrick J. Wong
2026-09-24 9:59 ` [PATCH 13/21] xfs: require file system block size alignment when using data checksums Christoph Hellwig
2026-09-25 23:24 ` Darrick J. Wong
2026-09-26 6:15 ` Christoph Hellwig
2026-09-24 9:59 ` [PATCH 14/21] xfs: add support for reading with " Christoph Hellwig
2026-09-29 0:42 ` Darrick J. Wong
2026-10-05 12:59 ` Christoph Hellwig
2026-09-24 9:59 ` [PATCH 15/21] xfs: add support for writing " Christoph Hellwig
2026-09-29 1:01 ` Darrick J. Wong
2026-10-05 13:00 ` Christoph Hellwig
2026-09-24 9:59 ` [PATCH 16/21] xfs: add data checksum support to zoned garbage collection Christoph Hellwig
2026-09-29 1:06 ` Darrick J. Wong
2026-10-05 13:11 ` Christoph Hellwig
2026-09-24 9:59 ` [PATCH 17/21] xfs: verify data checksums during media verification Christoph Hellwig
2026-09-29 1:19 ` Darrick J. Wong
2026-10-05 13:13 ` Christoph Hellwig
2026-09-24 9:59 ` [PATCH 18/21] xfs: don't try to verify checksums on empty zones Christoph Hellwig
2026-09-29 1:25 ` Darrick J. Wong
2026-10-05 13:14 ` Christoph Hellwig
2026-10-08 11:43 ` Anuj gupta
2026-09-24 9:59 ` [PATCH 19/21] xfs: report RT data checksum information via XFS_FSOP_GEOM Christoph Hellwig
2026-09-29 1:26 ` Darrick J. Wong
2026-09-24 9:59 ` [PATCH 20/21] xfs: add an experimental feature warning for RT data checksums Christoph Hellwig
2026-09-29 1:27 ` Darrick J. Wong
2026-09-24 9:59 ` [PATCH 21/21] xfs: enable " Christoph Hellwig
2026-09-29 1:27 ` Darrick J. Wong
2026-10-05 13:16 ` Christoph Hellwig
2026-09-24 22:52 ` support for " Dave Chinner
2026-09-25 6:27 ` Christoph Hellwig
2026-09-27 22:59 ` Dave Chinner
2026-09-28 5:24 ` Christoph Hellwig
2026-09-29 14:11 ` Dave Chinner
2026-09-30 7:11 ` Dave Chinner
2026-10-05 13:53 ` Christoph Hellwig
2026-10-06 5:31 ` Dave Chinner
2026-10-07 13:46 ` 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=20260924214939.GG2705364@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--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