From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 5/5] xfs: avoid unnecessary waits in xfs_log_force_lsn()
Date: Thu, 22 Jul 2021 12:13:45 -0700 [thread overview]
Message-ID: <20210722191345.GK559212@magnolia> (raw)
In-Reply-To: <20210722015335.3063274-6-david@fromorbit.com>
On Thu, Jul 22, 2021 at 11:53:35AM +1000, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> Before waiting on a iclog in xfs_log_force_lsn(), we don't check to
> see if the iclog has already been completed and the contents on
> stable storage. We check for completed iclogs in xfs_log_force(), so
> we should do the same thing for xfs_log_force_lsn().
>
> This fixed some random up-to-30s pauses seen in unmounting
> filesystems in some tests. A log force ends up waiting on completed
> iclog, and that doesn't then get flushed (and hence the log force
> get completed) until the background log worker issues a log force
> that flushes the iclog in question. Then the unmount unblocks and
> continues.
>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
Heh.
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> fs/xfs/xfs_log.c | 47 +++++++++++++++++++++++++++++++++++++----------
> 1 file changed, 37 insertions(+), 10 deletions(-)
>
> diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
> index 7da42c0656e3..baee9871cd65 100644
> --- a/fs/xfs/xfs_log.c
> +++ b/fs/xfs/xfs_log.c
> @@ -3147,6 +3147,35 @@ xlog_state_switch_iclogs(
> log->l_iclog = iclog->ic_next;
> }
>
> +/*
> + * Force the iclog to disk and check if the iclog has been completed before
> + * xlog_force_iclog() returns. This can happen on synchronous (e.g.
> + * pmem) or fast async storage because we drop the icloglock to issue the IO.
> + * If completion has already occurred, tell the caller so that it can avoid an
> + * unnecessary wait on the iclog.
> + */
> +static int
> +xlog_force_and_check_iclog(
> + struct xlog_in_core *iclog,
> + bool *completed)
> +{
> + xfs_lsn_t lsn = be64_to_cpu(iclog->ic_header.h_lsn);
> + int error;
> +
> + *completed = false;
> + error = xlog_force_iclog(iclog);
> + if (error)
> + return error;
> +
> + /*
> + * If the iclog has already been completed and reused the header LSN
> + * will have been rewritten by completion
> + */
> + if (be64_to_cpu(iclog->ic_header.h_lsn) != lsn)
> + *completed = true;
> + return 0;
> +}
> +
> /*
> * Write out all data in the in-core log as of this exact moment in time.
> *
> @@ -3181,7 +3210,6 @@ xfs_log_force(
> {
> struct xlog *log = mp->m_log;
> struct xlog_in_core *iclog;
> - xfs_lsn_t lsn;
>
> XFS_STATS_INC(mp, xs_log_force);
> trace_xfs_log_force(mp, 0, _RET_IP_);
> @@ -3210,15 +3238,11 @@ xfs_log_force(
> } else if (iclog->ic_state == XLOG_STATE_ACTIVE) {
> if (atomic_read(&iclog->ic_refcnt) == 0) {
> /* We have exclusive access to this iclog. */
> - lsn = be64_to_cpu(iclog->ic_header.h_lsn);
> - if (xlog_force_iclog(iclog))
> + bool completed;
> +
> + if (xlog_force_and_check_iclog(iclog, &completed))
> goto out_error;
> - /*
> - * If the iclog has already been completed and reused
> - * the header LSN will have been rewritten. Don't wait
> - * on these iclogs that contain future modifications.
> - */
> - if (be64_to_cpu(iclog->ic_header.h_lsn) != lsn)
> + if (completed)
> goto out_unlock;
> } else {
> /*
> @@ -3258,6 +3282,7 @@ xlog_force_lsn(
> bool already_slept)
> {
> struct xlog_in_core *iclog;
> + bool completed;
>
> spin_lock(&log->l_icloglock);
> iclog = log->l_iclog;
> @@ -3295,10 +3320,12 @@ xlog_force_lsn(
> &log->l_icloglock);
> return -EAGAIN;
> }
> - if (xlog_force_iclog(iclog))
> + if (xlog_force_and_check_iclog(iclog, &completed))
> goto out_error;
> if (log_flushed)
> *log_flushed = 1;
> + if (completed)
> + goto out_unlock;
> break;
> case XLOG_STATE_WANT_SYNC:
> /*
> --
> 2.31.1
>
prev parent reply other threads:[~2021-07-22 19:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 1:53 [PATCH 0/5] xfs: fix log cache flush regressions Dave Chinner
2021-07-22 1:53 ` [PATCH 1/5] xfs: flush data dev on external log write Dave Chinner
2021-07-22 6:41 ` Christoph Hellwig
2021-07-22 15:52 ` Darrick J. Wong
2021-07-22 1:53 ` [PATCH 2/5] xfs: external logs need to flush data device Dave Chinner
2021-07-22 6:48 ` Christoph Hellwig
2021-07-22 18:14 ` Darrick J. Wong
2021-07-22 21:45 ` Dave Chinner
2021-07-22 23:10 ` Darrick J. Wong
2021-07-22 1:53 ` [PATCH 3/5] xfs: fix ordering violation between cache flushes and tail updates Dave Chinner
2021-07-22 7:06 ` Christoph Hellwig
2021-07-22 7:28 ` Dave Chinner
2021-07-22 19:12 ` Darrick J. Wong
2021-07-22 1:53 ` [PATCH 4/5] xfs: log forces imply data device cache flushes Dave Chinner
2021-07-22 7:14 ` Christoph Hellwig
2021-07-22 7:32 ` Dave Chinner
2021-07-22 19:30 ` Darrick J. Wong
2021-07-22 22:12 ` Dave Chinner
2021-07-22 23:13 ` Darrick J. Wong
2021-07-22 1:53 ` [PATCH 5/5] xfs: avoid unnecessary waits in xfs_log_force_lsn() Dave Chinner
2021-07-22 7:15 ` Christoph Hellwig
2021-07-22 19:13 ` Darrick J. Wong [this message]
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=20210722191345.GK559212@magnolia \
--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