From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org, hch@infradead.org
Subject: Re: [PATCH 4/5] xfs: drop inactive dquots before inactivating inodes
Date: Tue, 1 Jun 2021 12:53:24 -0700 [thread overview]
Message-ID: <20210601195324.GC26380@locust> (raw)
In-Reply-To: <20210601003506.GZ664593@dread.disaster.area>
On Tue, Jun 01, 2021 at 10:35:06AM +1000, Dave Chinner wrote:
> On Mon, May 31, 2021 at 03:41:13PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> >
> > During quotaoff, the incore inode scan to detach dquots from inodes
> > won't touch inodes that have lost their VFS state but haven't yet been
> > queued for reclaim. This isn't strictly a problem because we drop the
> > dquots at the end of inactivation, but if we detect this situation
> > before starting inactivation, we can drop the inactive dquots early to
> > avoid delaying quotaoff further.
> >
> > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> > ---
> > fs/xfs/xfs_super.c | 32 ++++++++++++++++++++++++++++----
> > 1 file changed, 28 insertions(+), 4 deletions(-)
> >
> >
> > diff --git a/fs/xfs/xfs_super.c b/fs/xfs/xfs_super.c
> > index a2dab05332ac..79f1cd1a0221 100644
> > --- a/fs/xfs/xfs_super.c
> > +++ b/fs/xfs/xfs_super.c
> > @@ -637,22 +637,46 @@ xfs_fs_destroy_inode(
> > struct inode *inode)
> > {
> > struct xfs_inode *ip = XFS_I(inode);
> > + struct xfs_mount *mp = ip->i_mount;
> >
> > trace_xfs_destroy_inode(ip);
> >
> > ASSERT(!rwsem_is_locked(&inode->i_rwsem));
> > - XFS_STATS_INC(ip->i_mount, vn_rele);
> > - XFS_STATS_INC(ip->i_mount, vn_remove);
> > + XFS_STATS_INC(mp, vn_rele);
> > + XFS_STATS_INC(mp, vn_remove);
> > +
> > + /*
> > + * If a quota type is turned off but we still have a dquot attached to
> > + * the inode, detach it before processing this inode to avoid delaying
> > + * quotaoff for longer than is necessary.
> > + *
> > + * The inode has no VFS state and hasn't been tagged for any kind of
> > + * reclamation, which means that iget, quotaoff, blockgc, and reclaim
> > + * will not touch it. It is therefore safe to do this locklessly
> > + * because we have the only reference here.
> > + */
> > + if (!XFS_IS_UQUOTA_ON(mp)) {
> > + xfs_qm_dqrele(ip->i_udquot);
> > + ip->i_udquot = NULL;
> > + }
> > + if (!XFS_IS_GQUOTA_ON(mp)) {
> > + xfs_qm_dqrele(ip->i_gdquot);
> > + ip->i_gdquot = NULL;
> > + }
> > + if (!XFS_IS_PQUOTA_ON(mp)) {
> > + xfs_qm_dqrele(ip->i_pdquot);
> > + ip->i_pdquot = NULL;
> > + }
> >
> > xfs_inactive(ip);
>
> Shouldn't we just make xfs_inactive() unconditionally detatch dquots
> rather than just in the conditional case it does now after attaching
> dquots because it has to make modifications? For inodes that don't
> require any inactivation work, we get the same thing, and for those
> that do running a few extra transactions before dropping the dquots
> isn't going to make a huge difference to the quotaoff latency....
Actually... the previous patch does exactly that. I'll drop this patch.
--D
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
next prev parent reply other threads:[~2021-06-01 19:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 22:40 [PATCHSET v2 0/5] xfs: clean up quotaoff inode walks Darrick J. Wong
2021-05-31 22:40 ` [PATCH 1/5] xfs: move the quotaoff dqrele inode walk into xfs_icache.c Darrick J. Wong
2021-05-31 22:41 ` [PATCH 2/5] xfs: detach inode dquots at the end of inactivation Darrick J. Wong
2021-06-01 0:09 ` Dave Chinner
2021-05-31 22:41 ` [PATCH 3/5] xfs: separate the dqrele_all inode grab logic from xfs_inode_walk_ag_grab Darrick J. Wong
2021-06-01 0:20 ` Dave Chinner
2021-06-01 19:50 ` Darrick J. Wong
2021-06-01 21:40 ` Dave Chinner
2021-06-01 23:15 ` Darrick J. Wong
2021-05-31 22:41 ` [PATCH 4/5] xfs: drop inactive dquots before inactivating inodes Darrick J. Wong
2021-06-01 0:35 ` Dave Chinner
2021-06-01 19:53 ` Darrick J. Wong [this message]
2021-05-31 22:41 ` [PATCH 5/5] xfs: move xfs_inew_wait call into xfs_dqrele_inode Darrick J. Wong
2021-06-01 0:47 ` 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=20210601195324.GC26380@locust \
--to=djwong@kernel.org \
--cc=david@fromorbit.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