From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Carlos Maiolino <cem@kernel.org>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 06/10] xfs: regularize iclog space accounting in xlog_write_partial
Date: Tue, 4 Nov 2025 15:53:09 -0800 [thread overview]
Message-ID: <20251104235309.GT196370@frogsfrogsfrogs> (raw)
In-Reply-To: <20251030144946.1372887-7-hch@lst.de>
On Thu, Oct 30, 2025 at 03:49:16PM +0100, Christoph Hellwig wrote:
> When xlog_write_partial splits a log region over multiple iclogs, it
> has to include the continuation ophder in the length requested for the
> new iclog. Currently is simply adds that to the request, which makes
> the accounting of the used space below look slightly different from the
> other users of iclog space that decrement it. To prepare for more code
> sharing, adding the ophdr size to the len variable before the call to
> xlog_write_get_more_iclog_space and then decrement it later.
>
> This changes the contents of len when xlog_write_get_more_iclog_space
> returns an error, but as nothing looks at len in that case the
> difference doesn't matter.
Ooops, sorry I missed this patch. :(
It makes sense to me that we have to account for the continuation when
asking for a fresh iclog, but now I have a question. In "xfs: improve
the calling convention for the xlog_write helpers", the len pointer
becomes xlog_write_data::bytes_left. In the context of this patch, I
guess that means "len" is the amount of log data that we still have to
write to the log, correct?
--D
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> fs/xfs/xfs_log.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
> index 93e99d1cc037..539b22dff2d1 100644
> --- a/fs/xfs/xfs_log.c
> +++ b/fs/xfs/xfs_log.c
> @@ -2048,10 +2048,10 @@ xlog_write_partial(
> * consumes hasn't been accounted to the lv we are
> * writing.
> */
> + *len += sizeof(struct xlog_op_header);
> error = xlog_write_get_more_iclog_space(ticket,
> - &iclog, log_offset,
> - *len + sizeof(struct xlog_op_header),
> - record_cnt, data_cnt);
> + &iclog, log_offset, *len, record_cnt,
> + data_cnt);
> if (error)
> return error;
>
> @@ -2064,6 +2064,7 @@ xlog_write_partial(
> ticket->t_curr_res -= sizeof(struct xlog_op_header);
> *log_offset += sizeof(struct xlog_op_header);
> *data_cnt += sizeof(struct xlog_op_header);
> + *len -= sizeof(struct xlog_op_header);
>
> /*
> * If rlen fits in the iclog, then end the region
> --
> 2.47.3
>
>
next prev parent reply other threads:[~2025-11-04 23:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 14:49 cleanup log item formatting v2 Christoph Hellwig
2025-10-30 14:49 ` [PATCH 01/10] xfs: add a xlog_write_one_vec helper Christoph Hellwig
2025-10-31 23:59 ` Darrick J. Wong
2025-10-30 14:49 ` [PATCH 02/10] xfs: set lv_bytes in xlog_write_one_vec Christoph Hellwig
2025-11-01 0:04 ` Darrick J. Wong
2025-11-03 10:43 ` Christoph Hellwig
2025-11-04 23:39 ` Darrick J. Wong
2025-11-05 13:27 ` Christoph Hellwig
2025-11-05 22:13 ` Darrick J. Wong
2025-10-30 14:49 ` [PATCH 03/10] xfs: improve the ->iop_format interface Christoph Hellwig
2025-11-01 0:15 ` Darrick J. Wong
2025-10-30 14:49 ` [PATCH 04/10] xfs: move struct xfs_log_iovec to xfs_log_priv.h Christoph Hellwig
2025-11-01 1:16 ` Darrick J. Wong
2025-10-30 14:49 ` [PATCH 05/10] xfs: move struct xfs_log_vec " Christoph Hellwig
2025-11-01 1:16 ` Darrick J. Wong
2025-10-30 14:49 ` [PATCH 06/10] xfs: regularize iclog space accounting in xlog_write_partial Christoph Hellwig
2025-11-04 23:53 ` Darrick J. Wong [this message]
2025-11-05 13:27 ` Christoph Hellwig
2025-10-30 14:49 ` [PATCH 07/10] xfs: improve the calling convention for the xlog_write helpers Christoph Hellwig
2025-11-01 3:26 ` Darrick J. Wong
2025-11-03 10:46 ` Christoph Hellwig
2025-11-04 23:40 ` Darrick J. Wong
2025-11-05 13:28 ` Christoph Hellwig
2025-10-30 14:49 ` [PATCH 08/10] xfs: add a xlog_write_space_left helper Christoph Hellwig
2025-11-01 3:27 ` Darrick J. Wong
2025-10-30 14:49 ` [PATCH 09/10] xfs: improve the iclog space assert in xlog_write_iovec Christoph Hellwig
2025-11-04 23:45 ` Darrick J. Wong
2025-10-30 14:49 ` [PATCH 10/10] xfs: factor out a xlog_write_space_advance helper Christoph Hellwig
2025-11-04 23:46 ` Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2025-11-12 12:14 cleanup log item formatting v3 Christoph Hellwig
2025-11-12 12:14 ` [PATCH 06/10] xfs: regularize iclog space accounting in xlog_write_partial Christoph Hellwig
2025-11-14 16:55 ` 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=20251104235309.GT196370@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=hch@lst.de \
--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;
as well as URLs for NNTP newsgroup(s).