From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 5/8] xfs: factor callbacks out of xlog_state_do_callback()
Date: Fri, 6 Sep 2019 08:17:55 +1000 [thread overview]
Message-ID: <20190905221755.GI1119@dread.disaster.area> (raw)
In-Reply-To: <20190905153907.GF2229799@magnolia>
On Thu, Sep 05, 2019 at 08:39:07AM -0700, Darrick J. Wong wrote:
> On Thu, Sep 05, 2019 at 06:47:14PM +1000, Dave Chinner wrote:
> > @@ -2795,31 +2831,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;
> >
> > @@ -2835,6 +2853,8 @@ xlog_state_do_callback(
> > iclog = iclog->ic_next;
> > } while (first_iclog != iclog);
> >
> > + funcdidcallbacks += cycled_icloglock;
>
> funcdidcallbacks is effectively a yes/no state flag, so maybe it should
> be turned into a boolean and this statement becomes:
>
> funcdidcallbacks |= cycled_icloglock;
Fixed. I renamed it to did_callbacks at the same time, just to be a
little less eye-bleedy...
> Though I guess we're not at huge risk of integer overflow and it
> controls whether or not we run a debugging check so maybe we don't care?
All that really matters is we don't need a branch to calculate it :P
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2019-09-05 22:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 8:47 [PATCH 1/8 v2] xfs: log race fixes and cleanups Dave Chinner
2019-09-05 8:47 ` [PATCH 1/8] xfs: push the AIL in xlog_grant_head_wake Dave Chinner
2019-09-05 15:18 ` Darrick J. Wong
2019-09-05 22:02 ` Dave Chinner
2019-09-05 8:47 ` [PATCH 2/8] xfs: fix missed wakeup on l_flush_wait Dave Chinner
2019-09-05 15:21 ` Darrick J. Wong
2019-09-05 8:47 ` [PATCH 3/8] xfs: prevent CIL push holdoff in log recovery Dave Chinner
2019-09-05 15:26 ` Darrick J. Wong
2019-09-05 22:10 ` Dave Chinner
2019-09-05 8:47 ` [PATCH 4/8] xfs: factor debug code out of xlog_state_do_callback() Dave Chinner
2019-09-05 15:30 ` Darrick J. Wong
2019-09-05 22:14 ` Dave Chinner
2019-09-05 8:47 ` [PATCH 5/8] xfs: factor callbacks " Dave Chinner
2019-09-05 15:39 ` Darrick J. Wong
2019-09-05 22:17 ` Dave Chinner [this message]
2019-09-05 8:47 ` [PATCH 6/8] xfs: factor iclog state processing " Dave Chinner
2019-09-05 15:45 ` Darrick J. Wong
2019-09-05 8:47 ` [PATCH 7/8] xfs: push iclog state cleaning into xlog_state_clean_log Dave Chinner
2019-09-05 15:48 ` Darrick J. Wong
2019-09-05 22:28 ` Dave Chinner
2019-09-05 8:47 ` [PATCH 8/8] xfs: push the grant head when the log head moves forward Dave Chinner
2019-09-05 16:00 ` Darrick J. Wong
2019-09-05 15:44 ` [PATCH 1/8 v2] xfs: log race fixes and cleanups Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2019-09-06 0:05 [PATCH0/8 v3] " Dave Chinner
2019-09-06 0:05 ` [PATCH 5/8] xfs: factor callbacks out of xlog_state_do_callback() Dave Chinner
2019-09-06 0:16 ` 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=20190905221755.GI1119@dread.disaster.area \
--to=david@fromorbit.com \
--cc=darrick.wong@oracle.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