From: "Darrick J. Wong" <djwong@kernel.org>
To: Stephen Zhang <starzhangzsd@gmail.com>
Cc: dchinner@redhat.com, zhangshida <zhangshida@kylinos.cn>,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v3] xfs: add check before calling xfs_mod_fdblocks
Date: Wed, 22 Jun 2022 18:15:37 -0700 [thread overview]
Message-ID: <YrO+uap429yrLKD6@magnolia> (raw)
In-Reply-To: <CANubcdXyM2t0M0Ks3=6Hm12_SVm50vGaTBboj5CBF2LygOkUog@mail.gmail.com>
On Wed, Jun 22, 2022 at 01:57:31PM +0800, Stephen Zhang wrote:
> > I understand that calling __xfs_ag_resv_init on an AG with a maximally
> > sized data structure can result in @hidden_space being zero here, but
> > why does that matter enough to change the code? Are you experiencing
> > problems when this happens? Unnecessary slowdowns at mount time?
> > Something else?
> >
> > This is v3 of a patch and I still can't tell why I should care ...?
>
> After applying this patch, we can avoid to call xfs_mod_fdblocks when
> delta equals 0. So we can reduce unnecessary operations here.
Yeah, I get that, but what is the real world impact of those unnecessary
operations? Have you run fstests to make sure this change doesn't trip
over some weird subtlety in the code? Do the anticipated benefits
justify diverting my time to figuring out if we've really covered all
the corner cases?
IOWS: don't waste our time on theoretical improvements. There are
/plenty/ of things in 5.19 that need real attention, like generic/522
corrupting things and recoveryloop tests that trip over log recovery.
--D
prev parent reply other threads:[~2022-06-23 1:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 8:42 [PATCH v3] xfs: add check before calling xfs_mod_fdblocks Shida Zhang
2022-06-22 4:41 ` Darrick J. Wong
2022-06-22 5:57 ` Stephen Zhang
2022-06-23 1:15 ` Darrick J. Wong [this message]
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=YrO+uap429yrLKD6@magnolia \
--to=djwong@kernel.org \
--cc=dchinner@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=starzhangzsd@gmail.com \
--cc=zhangshida@kylinos.cn \
/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