From: Gao Xiang <hsiangkao@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: get rid of unnecessary xfs_perag_{get,put} pairs
Date: Wed, 3 Jun 2020 08:49:16 +0800 [thread overview]
Message-ID: <20200603004916.GA16546@xiangao.remote.csb> (raw)
In-Reply-To: <20200603002222.GU8230@magnolia>
Hi Darrick,
On Tue, Jun 02, 2020 at 05:22:22PM -0700, Darrick J. Wong wrote:
> On Tue, Jun 02, 2020 at 10:52:38PM +0800, Gao Xiang wrote:
> > Sometimes no need to play with perag_tree since for many
> > cases perag can also be accessed by agbp reliably.
> >
> > Signed-off-by: Gao Xiang <hsiangkao@redhat.com>
> > ---
> > Not sure addressing all the cases, but seems mostly.
> > Kindly correct me if something wrong somewhere...
> >
> > fs/xfs/libxfs/xfs_ag.c | 4 ++--
> > fs/xfs/libxfs/xfs_alloc.c | 22 ++++++-----------
> > fs/xfs/libxfs/xfs_alloc_btree.c | 10 ++++----
> > fs/xfs/libxfs/xfs_ialloc.c | 28 ++++++----------------
> > fs/xfs/libxfs/xfs_refcount_btree.c | 5 ++--
> > fs/xfs/libxfs/xfs_rmap_btree.c | 5 ++--
> > fs/xfs/xfs_inode.c | 38 +++++++++---------------------
> > 7 files changed, 35 insertions(+), 77 deletions(-)
> >
> > diff --git a/fs/xfs/libxfs/xfs_ag.c b/fs/xfs/libxfs/xfs_ag.c
> > index 9d84007a5c65..8cf73fe4338e 100644
> > --- a/fs/xfs/libxfs/xfs_ag.c
> > +++ b/fs/xfs/libxfs/xfs_ag.c
> > @@ -563,7 +563,8 @@ xfs_ag_get_geometry(
> > error = xfs_alloc_read_agf(mp, NULL, agno, 0, &agf_bp);
> > if (error)
> > goto out_agi;
> > - pag = xfs_perag_get(mp, agno);
> > +
> > + pag = agi_bp->b_pag;
> >
> > /* Fill out form. */
> > memset(ageo, 0, sizeof(*ageo));
> > @@ -583,7 +584,6 @@ xfs_ag_get_geometry(
> > xfs_ag_geom_health(pag, ageo);
> >
> > /* Release resources. */
> > - xfs_perag_put(pag);
>
> Looks like a reaosnable pattern throughout the codebase. Did fstests
> cough up any new errors?
Actually I add more extra ASSERTs (to check pag_agno vs agno) around
all the cases (many of them aren't shown in this patch), and have been
running fstests and fsstress with ASSERT version for a while. It seems
no visible crash. But I'm not sure how many exist failures are (at least
no panic yells out)...
>
> > xfs_buf_relse(agf_bp);
...
> > - xfs_perag_put(pag);
> > - return error;
> > + /* Point the head of the list to the next unlinked inode. */
> > + return xfs_iunlink_update_bucket(tp, agno, agibp, bucket_index,
> > + next_agino);
>
> Why not cut out the agno argument here too? Surely you could obtain it
> from agibp->b_pag->pag_agno. Ditto for xfs_iunlink_map_prev.
Okay, thanks for pointing out... I think there are many indirect
potential cleanups indeed.... Will fix the above cases in the
next version...
Thanks,
Gao Xiang
>
> --D
>
> > }
> >
> > /*
> > --
> > 2.18.1
> >
>
next prev parent reply other threads:[~2020-06-03 0:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 14:52 [PATCH] xfs: get rid of unnecessary xfs_perag_{get,put} pairs Gao Xiang
2020-06-03 0:22 ` Darrick J. Wong
2020-06-03 0:44 ` Dave Chinner
2020-06-03 0:48 ` Darrick J. Wong
2020-06-03 0:49 ` Gao Xiang [this message]
2020-06-03 1:27 ` Dave Chinner
2020-06-03 1:40 ` Gao Xiang
2020-06-03 3:02 ` Dave Chinner
2020-06-03 3:19 ` Gao Xiang
2020-06-03 12:11 ` [PATCH v2] " Gao Xiang
2020-06-04 21:59 ` Dave Chinner
2020-06-05 1:44 ` Gao Xiang
2020-06-05 8:52 ` [PATCH v3] " Gao Xiang
2020-06-05 15:56 ` Darrick J. Wong
2020-06-05 18:30 ` Gao Xiang
2020-06-05 18:47 ` Gao Xiang
2020-06-23 10:08 ` Gao Xiang
2020-07-13 8:53 ` [PATCH v4] " Gao Xiang
2020-07-13 16:12 ` 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=20200603004916.GA16546@xiangao.remote.csb \
--to=hsiangkao@redhat.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;
as well as URLs for NNTP newsgroup(s).