From: Qu Wenruo <wqu@suse.com>
To: JunChao Sun <sunjunchao2870@gmail.com>,
Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: linux-btrfs@vger.kernel.org, clm@fb.com, josef@toxicpanda.com,
dsterba@suse.com
Subject: Re: [PATCH v2] btrfs: qgroup: use xarray to track dirty extents in transaction.
Date: Fri, 7 Jun 2024 07:34:45 +0930 [thread overview]
Message-ID: <b0d99324-0e1f-453a-800d-e1967a87a997@suse.com> (raw)
In-Reply-To: <CAHB1NajCcMA_VeBndEd2HMB=wbrX4iLYZGpb_jyw7mcd0Pyhwg@mail.gmail.com>
在 2024/6/6 21:32, JunChao Sun 写道:
[...]
>>> We have qgroup_mark_inconsistent(), which would skip future accounting.
>
> Yeh. I saw this function. But it sets the
> BTRFS_QGROUP_RUNTIME_FLAG_NO_ACCOUNTING flag, which will skip some
> accounting.
> Do you mean that there's no need to account for this inconsistent state?
Yes, since the numbers are no longer correct, there is no more need to
do the accounting.
That would save a lot of CPU and IO.
Thanks,
Qu
prev parent reply other threads:[~2024-06-06 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 11:36 [PATCH v2] btrfs: qgroup: use xarray to track dirty extents in transaction Junchao Sun
2024-06-06 9:30 ` Qu Wenruo
2024-06-06 12:02 ` JunChao Sun
2024-06-06 22:04 ` Qu Wenruo [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=b0d99324-0e1f-453a-800d-e1967a87a997@suse.com \
--to=wqu@suse.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=sunjunchao2870@gmail.com \
/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