From: Brian Foster <bfoster@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 06/14] xfs: reset dfops to initial state after finish
Date: Thu, 19 Jul 2018 16:33:38 -0400 [thread overview]
Message-ID: <20180719203338.GH29404@bfoster> (raw)
In-Reply-To: <20180719195441.GG6558@infradead.org>
On Thu, Jul 19, 2018 at 12:54:41PM -0700, Christoph Hellwig wrote:
> On Thu, Jul 19, 2018 at 09:49:11AM -0400, Brian Foster wrote:
> > xfs_defer_init() is currently used in two particular situations. The
> > first and most obvious case is raw initialization of an
> > xfs_defer_ops struct. The other case is partial reinit of
> > xfs_defer_ops on reuse due to iteration.
> >
> > Most instances of the first case will be replaced by a single init
> > of a dfops embedded in the transaction. Init calls are still
> > technically required for the second case because the dfops may have
> > low space mode enabled or have joined items that need to be reset
> > before the dfops should be reused.
> >
> > Since the current dfops usage expects either a final transaction
> > commit after xfs_defer_finish() or xfs_defer_init() if dfops is to
> > be reused, we can shift some of the init logic into
> > xfs_defer_finish() such that the latter returns with a reinitialized
> > dfops. This eliminates the second dependency noted above such that a
> > dfops is immediately ready for reuse after an xfs_defer_finish()
> > without the need to change any calling code.
> >
> > Signed-off-by: Brian Foster <bfoster@redhat.com>
> > ---
> > fs/xfs/libxfs/xfs_defer.c | 30 ++++++++++++++++++++++++++++--
> > 1 file changed, 28 insertions(+), 2 deletions(-)
> >
> > diff --git a/fs/xfs/libxfs/xfs_defer.c b/fs/xfs/libxfs/xfs_defer.c
> > index d3466087db16..e6baa27a690b 100644
> > --- a/fs/xfs/libxfs/xfs_defer.c
> > +++ b/fs/xfs/libxfs/xfs_defer.c
> > @@ -319,6 +319,29 @@ xfs_defer_bjoin(
> > return -EFSCORRUPTED;
> > }
> >
> > +/*
> > + * Reset an already used dfops after finish.
> > + */
> > +static void
> > +xfs_defer_reset(
> > + struct xfs_defer_ops *dop)
> > +{
> > + int i;
> > +
> > + ASSERT(!xfs_defer_has_unfinished_work(dop));
> > + dop->dop_low = false;
> > + for (i = 0; i < XFS_DEFER_OPS_NR_INODES; i++) {
> > + if (!dop->dop_inodes[i])
> > + break;
> > + dop->dop_inodes[i] = NULL;
> > + }
> > + for (i = 0; i < XFS_DEFER_OPS_NR_BUFS; i++) {
> > + if (!dop->dop_bufs[i])
> > + break;
> > + dop->dop_bufs[i] = NULL;
> > + }
> > +}
>
> Are these loops really more efficient than just doing memsets
> of dop_inodes and dop_bufs?
>
Not sure, I suppose we could just check dop_bufs[0] and memset() if !=
NULL..? I can do that as well if we don't otherwise lose these pointers.
Brian
> Otherwise looks good:
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2018-07-19 21:18 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 13:49 [PATCH 00/14] xfs: embed dfops in the transaction Brian Foster
2018-07-19 13:49 ` [PATCH 01/14] xfs: pull up dfops from xfs_itruncate_extents() Brian Foster
2018-07-19 19:50 ` Christoph Hellwig
2018-07-19 13:49 ` [PATCH 02/14] xfs: use ->t_dfops in log recovery intent processing Brian Foster
2018-07-19 19:50 ` Christoph Hellwig
2018-07-19 13:49 ` [PATCH 03/14] xfs: fix transaction leak on remote attr set/remove failure Brian Foster
2018-07-19 19:51 ` Christoph Hellwig
2018-07-19 13:49 ` [PATCH 04/14] xfs: make deferred processing safe for embedded dfops Brian Foster
2018-07-19 19:52 ` Christoph Hellwig
2018-07-19 13:49 ` [PATCH 05/14] xfs: remove unused deferred ops committed field Brian Foster
2018-07-19 19:53 ` Christoph Hellwig
2018-07-19 13:49 ` [PATCH 06/14] xfs: reset dfops to initial state after finish Brian Foster
2018-07-19 19:54 ` Christoph Hellwig
2018-07-19 20:33 ` Brian Foster [this message]
2018-07-20 16:07 ` Christoph Hellwig
2018-07-19 13:49 ` [PATCH 07/14] xfs: pack holes in xfs_defer_ops and xfs_trans Brian Foster
2018-07-19 19:54 ` Christoph Hellwig
2018-07-19 13:49 ` [PATCH 08/14] xfs: support embedded dfops in transaction Brian Foster
2018-07-19 16:18 ` Brian Foster
2018-07-19 19:47 ` Christoph Hellwig
2018-07-19 20:31 ` Brian Foster
2018-07-20 16:05 ` Christoph Hellwig
2018-07-20 16:27 ` Darrick J. Wong
2018-07-19 19:56 ` Christoph Hellwig
2018-07-19 20:32 ` Brian Foster
2018-07-20 16:06 ` Christoph Hellwig
2018-07-19 13:49 ` [PATCH 09/14] xfs: use internal dfops in cow blocks cancel Brian Foster
2018-07-19 19:57 ` Christoph Hellwig
2018-07-19 20:33 ` Brian Foster
2018-07-19 13:49 ` [PATCH 10/14] xfs: use internal dfops in attr code Brian Foster
2018-07-19 13:49 ` [PATCH 11/14] xfs: use internal dfops during [b|c]ui recovery Brian Foster
2018-07-19 13:49 ` [PATCH 12/14] xfs: remove all boilerplate defer init/finish code Brian Foster
2018-07-19 13:49 ` [PATCH 13/14] xfs: remove unnecessary dfops init calls in xattr code Brian Foster
2018-07-19 13:49 ` [PATCH 14/14] xfs: drop unnecessary xfs_defer_finish() dfops parameter Brian Foster
2018-07-19 20:05 ` [PATCH 00/14] xfs: embed dfops in the transaction Christoph Hellwig
2018-07-19 20:36 ` Brian Foster
2018-07-19 21:36 ` Darrick J. Wong
2018-07-20 14:06 ` Brian Foster
2018-07-20 14:41 ` Brian Foster
2018-07-20 16:11 ` Christoph Hellwig
2018-07-20 16:09 ` Christoph Hellwig
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=20180719203338.GH29404@bfoster \
--to=bfoster@redhat.com \
--cc=hch@infradead.org \
--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).