From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org, hch@infradead.org
Subject: Re: [PATCH 5/6] xfs: merge xfs_reclaim_inodes_ag into xfs_inode_walk_ag
Date: Fri, 26 Mar 2021 06:30:56 +0000 [thread overview]
Message-ID: <20210326063056.GF3421955@infradead.org> (raw)
In-Reply-To: <161671810078.621936.339407186528826628.stgit@magnolia>
On Thu, Mar 25, 2021 at 05:21:40PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> Merge these two inode walk loops together, since they're pretty similar
> now. Get rid of XFS_ICI_NO_TAG since nobody uses it.
The laster user of XFS_ICI_NO_TAG was quotoff, and the last reference
was removed in "xfs: remove indirect calls from xfs_inode_walk{,_ag}".
So I think it should be dropped there, or even better in a prep patch
removing all the XFS_ICI_NO_TAG code before that one.
> +static inline bool
> +selected_for_walk(
> + unsigned int tag,
> + struct xfs_inode *ip)
> +{
> + switch (tag) {
> + case XFS_ICI_BLOCKGC_TAG:
> + return xfs_blockgc_grab(ip);
> + case XFS_ICI_RECLAIM_TAG:
> + return xfs_reclaim_inode_grab(ip);
> + default:
> + return false;
> + }
> +}
Maybe name ths something that starts with xfs_ and ends with _grab?
> * and release all incore inodes with the given radix tree @tag.
> @@ -786,12 +803,14 @@ xfs_inode_walk_ag(
> bool done;
> int nr_found;
>
> - ASSERT(tag == XFS_ICI_BLOCKGC_TAG);
> + ASSERT(tag < RADIX_TREE_MAX_TAGS);
>
> restart:
> done = false;
> skipped = 0;
> first_index = 0;
> + if (tag == XFS_ICI_RECLAIM_TAG)
> + first_index = READ_ONCE(pag->pag_ici_reclaim_cursor);
if / else to make this clear?
> for (i = 0; i < nr_found; i++) {
> if (!batch[i])
> continue;
> - error = xfs_blockgc_scan_inode(batch[i], eofb);
> - xfs_irele(batch[i]);
> + switch (tag) {
> + case XFS_ICI_BLOCKGC_TAG:
> + error = xfs_blockgc_scan_inode(batch[i], eofb);
> + xfs_irele(batch[i]);
> + break;
> + case XFS_ICI_RECLAIM_TAG:
> + xfs_reclaim_inode(batch[i], pag);
> + error = 0;
Maybe move the irele into xfs_blockgc_scan_inode to make the calling
conventions more similar?
next prev parent reply other threads:[~2021-03-26 6:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 0:21 [PATCHSET v3 0/6] xfs: clean up incore inode walk functions Darrick J. Wong
2021-03-26 0:21 ` [PATCH 1/6] xfs: use s_inodes in xfs_qm_dqrele_all_inodes Darrick J. Wong
2021-03-30 0:44 ` Dave Chinner
2021-03-30 2:36 ` Darrick J. Wong
2021-03-30 3:07 ` Dave Chinner
2021-03-30 4:06 ` Darrick J. Wong
2021-03-31 1:34 ` Dave Chinner
2021-03-26 0:21 ` [PATCH 2/6] xfs: remove iter_flags parameter from xfs_inode_walk_* Darrick J. Wong
2021-03-26 6:04 ` Christoph Hellwig
2021-03-26 0:21 ` [PATCH 3/6] xfs: remove indirect calls from xfs_inode_walk{,_ag} Darrick J. Wong
2021-03-26 6:08 ` Christoph Hellwig
2021-03-26 0:21 ` [PATCH 4/6] xfs: pass struct xfs_eofblocks to the inode scan callback Darrick J. Wong
2021-03-26 6:09 ` Christoph Hellwig
2021-03-26 0:21 ` [PATCH 5/6] xfs: merge xfs_reclaim_inodes_ag into xfs_inode_walk_ag Darrick J. Wong
2021-03-26 6:30 ` Christoph Hellwig [this message]
2021-03-26 16:07 ` Darrick J. Wong
2021-03-26 0:21 ` [PATCH 6/6] xfs: refactor per-AG inode tagging functions Darrick J. Wong
2021-03-26 6:48 ` Christoph Hellwig
2021-03-26 16:34 ` 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=20210326063056.GF3421955@infradead.org \
--to=hch@infradead.org \
--cc=djwong@kernel.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).