From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 5/8] xfs: factor callbacks out of xlog_state_do_callback()
Date: Thu, 5 Sep 2019 17:16:42 -0700 [thread overview]
Message-ID: <20190906001642.GN2229799@magnolia> (raw)
In-Reply-To: <20190906000553.6740-6-david@fromorbit.com>
On Fri, Sep 06, 2019 at 10:05:50AM +1000, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> Simplify the code flow by lifting the iclog callback work out of
> the main iclog iteration loop. This isolates the log juggling and
> callbacks from the iclog state change logic in the loop.
>
> Note that the loopdidcallbacks variable is not actually tracking
> whether callbacks are actually run - it is tracking whether the
> icloglock was dropped during the loop and so determines if we
> completed the entire iclog scan loop atomically. Hence we know for
> certain there are either no more ordered completions to run or
> that the next completion will run the remaining ordered iclog
> completions. Hence rename that variable appropriately for it's
> function.
>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
LGTM,
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
> ---
> fs/xfs/xfs_log.c | 76 ++++++++++++++++++++++++++++++------------------
> 1 file changed, 48 insertions(+), 28 deletions(-)
>
> diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
> index ff495c52807b..65088a810ad3 100644
> --- a/fs/xfs/xfs_log.c
> +++ b/fs/xfs/xfs_log.c
> @@ -2634,6 +2634,42 @@ xlog_get_lowest_lsn(
> return lowest_lsn;
> }
>
> +/*
> + * Keep processing entries in the iclog callback list until we come around and
> + * it is empty. We need to atomically see that the list is empty and change the
> + * state to DIRTY so that we don't miss any more callbacks being added.
> + *
> + * This function is called with the icloglock held and returns with it held. We
> + * drop it while running callbacks, however, as holding it over thousands of
> + * callbacks is unnecessary and causes excessive contention if we do.
> + */
> +static void
> +xlog_state_do_iclog_callbacks(
> + struct xlog *log,
> + struct xlog_in_core *iclog,
> + bool aborted)
> +{
> + spin_unlock(&log->l_icloglock);
> + spin_lock(&iclog->ic_callback_lock);
> + while (!list_empty(&iclog->ic_callbacks)) {
> + LIST_HEAD(tmp);
> +
> + list_splice_init(&iclog->ic_callbacks, &tmp);
> +
> + spin_unlock(&iclog->ic_callback_lock);
> + xlog_cil_process_committed(&tmp, aborted);
> + spin_lock(&iclog->ic_callback_lock);
> + }
> +
> + /*
> + * Pick up the icloglock while still holding the callback lock so we
> + * serialise against anyone trying to add more callbacks to this iclog
> + * now we've finished processing.
> + */
> + spin_lock(&log->l_icloglock);
> + spin_unlock(&iclog->ic_callback_lock);
> +}
> +
> #ifdef DEBUG
> /*
> * Make one last gasp attempt to see if iclogs are being left in limbo. If the
> @@ -2688,15 +2724,15 @@ xlog_state_do_callback(
> int flushcnt = 0;
> xfs_lsn_t lowest_lsn;
> int ioerrors; /* counter: iclogs with errors */
> - int loopdidcallbacks; /* flag: inner loop did callbacks*/
> - int funcdidcallbacks; /* flag: function did callbacks */
> + bool cycled_icloglock;
> + bool did_callbacks;
> int repeats; /* for issuing console warnings if
> * looping too many times */
>
> spin_lock(&log->l_icloglock);
> first_iclog = iclog = log->l_iclog;
> ioerrors = 0;
> - funcdidcallbacks = 0;
> + did_callbacks = 0;
> repeats = 0;
>
> do {
> @@ -2710,7 +2746,7 @@ xlog_state_do_callback(
> */
> first_iclog = log->l_iclog;
> iclog = log->l_iclog;
> - loopdidcallbacks = 0;
> + cycled_icloglock = false;
> repeats++;
>
> do {
> @@ -2801,31 +2837,13 @@ xlog_state_do_callback(
> } else
> ioerrors++;
>
> - spin_unlock(&log->l_icloglock);
> -
> /*
> - * Keep processing entries in the callback list until
> - * we come around and it is empty. We need to
> - * atomically see that the list is empty and change the
> - * state to DIRTY so that we don't miss any more
> - * callbacks being added.
> + * Running callbacks will drop the icloglock which means
> + * we'll have to run at least one more complete loop.
> */
> - spin_lock(&iclog->ic_callback_lock);
> - while (!list_empty(&iclog->ic_callbacks)) {
> - LIST_HEAD(tmp);
> + cycled_icloglock = true;
> + xlog_state_do_iclog_callbacks(log, iclog, aborted);
>
> - list_splice_init(&iclog->ic_callbacks, &tmp);
> -
> - spin_unlock(&iclog->ic_callback_lock);
> - xlog_cil_process_committed(&tmp, aborted);
> - spin_lock(&iclog->ic_callback_lock);
> - }
> -
> - loopdidcallbacks++;
> - funcdidcallbacks++;
> -
> - spin_lock(&log->l_icloglock);
> - spin_unlock(&iclog->ic_callback_lock);
> if (!(iclog->ic_state & XLOG_STATE_IOERROR))
> iclog->ic_state = XLOG_STATE_DIRTY;
>
> @@ -2841,6 +2859,8 @@ xlog_state_do_callback(
> iclog = iclog->ic_next;
> } while (first_iclog != iclog);
>
> + did_callbacks |= cycled_icloglock;
> +
> if (repeats > 5000) {
> flushcnt += repeats;
> repeats = 0;
> @@ -2848,9 +2868,9 @@ xlog_state_do_callback(
> "%s: possible infinite loop (%d iterations)",
> __func__, flushcnt);
> }
> - } while (!ioerrors && loopdidcallbacks);
> + } while (!ioerrors && cycled_icloglock);
>
> - if (funcdidcallbacks)
> + if (did_callbacks)
> xlog_state_callback_check_state(log);
>
> if (log->l_iclog->ic_state & (XLOG_STATE_ACTIVE|XLOG_STATE_IOERROR))
> --
> 2.23.0.rc1
>
next prev parent reply other threads:[~2019-09-06 0:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 0:05 [PATCH0/8 v3] xfs: log race fixes and cleanups Dave Chinner
2019-09-06 0:05 ` [PATCH 1/8] xfs: push the AIL in xlog_grant_head_wake Dave Chinner
2019-09-06 0:12 ` Darrick J. Wong
2019-09-06 0:05 ` [PATCH 2/8] xfs: fix missed wakeup on l_flush_wait Dave Chinner
2019-09-06 0:05 ` [PATCH 3/8] xfs: prevent CIL push holdoff in log recovery Dave Chinner
2019-09-06 0:15 ` Darrick J. Wong
2019-09-06 2:01 ` Dave Chinner
2019-09-06 2:08 ` [PATCH 3/8 v2] " Dave Chinner
2019-09-06 3:01 ` Darrick J. Wong
2019-09-06 0:05 ` [PATCH 4/8] xfs: factor debug code out of xlog_state_do_callback() Dave Chinner
2019-09-06 0:05 ` [PATCH 5/8] xfs: factor callbacks " Dave Chinner
2019-09-06 0:16 ` Darrick J. Wong [this message]
2019-09-06 0:05 ` [PATCH 6/8] xfs: factor iclog state processing " Dave Chinner
2019-09-06 0:05 ` [PATCH 7/8] xfs: push iclog state cleaning into xlog_state_clean_log Dave Chinner
2019-09-06 0:05 ` [PATCH 8/8] xfs: push the grant head when the log head moves forward Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2019-09-05 8:47 [PATCH 1/8 v2] xfs: log race fixes and cleanups Dave Chinner
2019-09-05 8:47 ` [PATCH 5/8] xfs: factor callbacks out of xlog_state_do_callback() Dave Chinner
2019-09-05 15:39 ` Darrick J. Wong
2019-09-05 22:17 ` 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=20190906001642.GN2229799@magnolia \
--to=darrick.wong@oracle.com \
--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