From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 4/8] xfs: pass a CIL context to xlog_write()
Date: Thu, 17 Jun 2021 13:24:02 -0700 [thread overview]
Message-ID: <20210617202402.GX158209@locust> (raw)
In-Reply-To: <20210617082617.971602-5-david@fromorbit.com>
On Thu, Jun 17, 2021 at 06:26:13PM +1000, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> Pass the CIL context to xlog_write() rather than a pointer to a LSN
> variable. Only the CIL checkpoint calls to xlog_write() need to know
> about the start LSN of the writes, so rework xlog_write to directly
> write the LSNs into the CIL context structure.
>
> This removes the commit_lsn variable from xlog_cil_push_work(), so
> now we only have to issue the commit record ordering wakeup from
> there.
>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> ---
> fs/xfs/xfs_log.c | 22 +++++++++++++++++-----
> fs/xfs/xfs_log_cil.c | 19 ++++++++-----------
> fs/xfs/xfs_log_priv.h | 4 ++--
> 3 files changed, 27 insertions(+), 18 deletions(-)
>
> diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
> index cf661c155786..fc0e43c57683 100644
> --- a/fs/xfs/xfs_log.c
> +++ b/fs/xfs/xfs_log.c
> @@ -871,7 +871,7 @@ xlog_write_unmount_record(
> */
> if (log->l_targ != log->l_mp->m_ddev_targp)
> blkdev_issue_flush(log->l_targ->bt_bdev);
> - return xlog_write(log, &lv_chain, ticket, NULL, NULL, reg.i_len);
> + return xlog_write(log, NULL, &lv_chain, ticket, NULL, reg.i_len);
> }
>
> /*
> @@ -2383,9 +2383,9 @@ xlog_write_partial(
> int
> xlog_write(
> struct xlog *log,
> + struct xfs_cil_ctx *ctx,
> struct list_head *lv_chain,
> struct xlog_ticket *ticket,
> - xfs_lsn_t *start_lsn,
> struct xlog_in_core **commit_iclog,
> uint32_t len)
> {
> @@ -2408,9 +2408,21 @@ xlog_write(
> if (error)
> return error;
>
> - /* start_lsn is the LSN of the first iclog written to. */
> - if (start_lsn)
> - *start_lsn = be64_to_cpu(iclog->ic_header.h_lsn);
> + /*
> + * If we have a CIL context, record the LSN of the iclog we were just
> + * granted space to start writing into. If the context doesn't have
> + * a start_lsn recorded, then this iclog will contain the start record
> + * for the checkpoint. Otherwise this write contains the commit record
> + * for the checkpoint.
> + */
> + if (ctx) {
> + spin_lock(&ctx->cil->xc_push_lock);
> + if (!ctx->start_lsn)
> + ctx->start_lsn = be64_to_cpu(iclog->ic_header.h_lsn);
> + else
> + ctx->commit_lsn = be64_to_cpu(iclog->ic_header.h_lsn);
> + spin_unlock(&ctx->cil->xc_push_lock);
This cycling of the push lock when setting start_lsn is new. What are
we protecting against here by taking the lock?
Also, just to check my assumptions: why do we take the push lock when
setting commit_lsn? Is that to synchronize with the xc_committing loop
that looks for contexts that need pushing?
--D
> + }
>
> lv = list_first_entry_or_null(lv_chain, struct xfs_log_vec, lv_list);
> while (lv) {
> diff --git a/fs/xfs/xfs_log_cil.c b/fs/xfs/xfs_log_cil.c
> index 2c8b25888c53..35fc3e57d870 100644
> --- a/fs/xfs/xfs_log_cil.c
> +++ b/fs/xfs/xfs_log_cil.c
> @@ -790,14 +790,13 @@ xlog_cil_build_trans_hdr(
> */
> int
> xlog_cil_write_commit_record(
> - struct xlog *log,
> - struct xlog_ticket *ticket,
> - struct xlog_in_core **iclog,
> - xfs_lsn_t *lsn)
> + struct xfs_cil_ctx *ctx,
> + struct xlog_in_core **iclog)
> {
> + struct xlog *log = ctx->cil->xc_log;
> struct xlog_op_header ophdr = {
> .oh_clientid = XFS_TRANSACTION,
> - .oh_tid = cpu_to_be32(ticket->t_tid),
> + .oh_tid = cpu_to_be32(ctx->ticket->t_tid),
> .oh_flags = XLOG_COMMIT_TRANS,
> };
> struct xfs_log_iovec reg = {
> @@ -818,8 +817,8 @@ xlog_cil_write_commit_record(
> return -EIO;
>
> /* account for space used by record data */
> - ticket->t_curr_res -= reg.i_len;
> - error = xlog_write(log, &lv_chain, ticket, lsn, iclog, reg.i_len);
> + ctx->ticket->t_curr_res -= reg.i_len;
> + error = xlog_write(log, ctx, &lv_chain, ctx->ticket, iclog, reg.i_len);
> if (error)
> xfs_force_shutdown(log->l_mp, SHUTDOWN_LOG_IO_ERROR);
> return error;
> @@ -1038,7 +1037,7 @@ xlog_cil_push_work(
> * use the commit record lsn then we can move the tail beyond the grant
> * write head.
> */
> - error = xlog_write(log, &ctx->lv_chain, ctx->ticket, &ctx->start_lsn,
> + error = xlog_write(log, ctx, &ctx->lv_chain, ctx->ticket,
> NULL, num_bytes);
>
> /*
> @@ -1083,8 +1082,7 @@ xlog_cil_push_work(
> }
> spin_unlock(&cil->xc_push_lock);
>
> - error = xlog_cil_write_commit_record(log, ctx->ticket, &commit_iclog,
> - &commit_lsn);
> + error = xlog_cil_write_commit_record(ctx, &commit_iclog);
> if (error)
> goto out_abort_free_ticket;
>
> @@ -1104,7 +1102,6 @@ xlog_cil_push_work(
> * and wake up anyone who is waiting for the commit to complete.
> */
> spin_lock(&cil->xc_push_lock);
> - ctx->commit_lsn = commit_lsn;
> wake_up_all(&cil->xc_commit_wait);
> spin_unlock(&cil->xc_push_lock);
>
> diff --git a/fs/xfs/xfs_log_priv.h b/fs/xfs/xfs_log_priv.h
> index 26f26769d1c6..af8a9dfa8068 100644
> --- a/fs/xfs/xfs_log_priv.h
> +++ b/fs/xfs/xfs_log_priv.h
> @@ -487,8 +487,8 @@ xlog_write_adv_cnt(void **ptr, int *len, int *off, size_t bytes)
>
> void xlog_print_tic_res(struct xfs_mount *mp, struct xlog_ticket *ticket);
> void xlog_print_trans(struct xfs_trans *);
> -int xlog_write(struct xlog *log, struct list_head *lv_chain,
> - struct xlog_ticket *tic, xfs_lsn_t *start_lsn,
> +int xlog_write(struct xlog *log, struct xfs_cil_ctx *ctx,
> + struct list_head *lv_chain, struct xlog_ticket *tic,
> struct xlog_in_core **commit_iclog, uint32_t len);
>
> void xfs_log_ticket_ungrant(struct xlog *log, struct xlog_ticket *ticket);
> --
> 2.31.1
>
next prev parent reply other threads:[~2021-06-17 20:24 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 8:26 [PATCH 0/8 V2] xfs: log fixes for for-next Dave Chinner
2021-06-17 8:26 ` [PATCH 1/8] xfs: add iclog state trace events Dave Chinner
2021-06-17 16:45 ` Darrick J. Wong
2021-06-18 14:09 ` Christoph Hellwig
2021-06-17 8:26 ` [PATCH 2/8] xfs: don't wait on future iclogs when pushing the CIL Dave Chinner
2021-06-17 17:49 ` Darrick J. Wong
2021-06-17 21:55 ` Dave Chinner
2021-06-17 8:26 ` [PATCH 3/8] xfs: move xlog_commit_record to xfs_log_cil.c Dave Chinner
2021-06-17 12:57 ` kernel test robot
2021-06-17 17:50 ` Darrick J. Wong
2021-06-17 21:56 ` Dave Chinner
2021-06-18 14:16 ` Christoph Hellwig
2021-06-17 8:26 ` [PATCH 4/8] xfs: pass a CIL context to xlog_write() Dave Chinner
2021-06-17 14:46 ` kernel test robot
2021-06-17 20:24 ` Darrick J. Wong [this message]
2021-06-17 22:03 ` Dave Chinner
2021-06-17 22:18 ` Darrick J. Wong
2021-06-18 14:23 ` Christoph Hellwig
2021-06-28 8:58 ` Dan Carpenter
2021-06-17 8:26 ` [PATCH 5/8] xfs: factor out log write ordering from xlog_cil_push_work() Dave Chinner
2021-06-17 19:59 ` Darrick J. Wong
2021-06-18 14:27 ` Christoph Hellwig
2021-06-18 22:34 ` Dave Chinner
2021-06-17 8:26 ` [PATCH 6/8] xfs: separate out setting CIL context LSNs from xlog_write Dave Chinner
2021-06-17 20:28 ` Darrick J. Wong
2021-06-17 22:10 ` Dave Chinner
2021-06-17 8:26 ` [PATCH 7/8] xfs: attached iclog callbacks in xlog_cil_set_ctx_write_state() Dave Chinner
2021-06-17 20:55 ` Darrick J. Wong
2021-06-17 22:20 ` Dave Chinner
2021-06-17 8:26 ` [PATCH 8/8] xfs: order CIL checkpoint start records Dave Chinner
2021-06-17 21:31 ` Darrick J. Wong
2021-06-17 22:49 ` Dave Chinner
2021-06-17 18:32 ` [PATCH 0/8 V2] xfs: log fixes for for-next Brian Foster
2021-06-17 19:05 ` Darrick J. Wong
2021-06-17 20:06 ` Brian Foster
2021-06-17 20:26 ` Darrick J. Wong
2021-06-17 23:31 ` Brian Foster
2021-06-17 23:43 ` Dave Chinner
2021-06-18 13:08 ` Brian Foster
2021-06-18 13:55 ` Christoph Hellwig
2021-06-18 14:02 ` Christoph Hellwig
2021-06-18 22:28 ` Dave Chinner
2021-06-18 22:15 ` Dave Chinner
2021-06-18 22:48 ` Dave Chinner
2021-06-19 20:22 ` Darrick J. Wong
2021-06-20 22:18 ` Dave Chinner
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=20210617202402.GX158209@locust \
--to=djwong@kernel.org \
--cc=david@fromorbit.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