From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Josef Bacik <josef@toxicpanda.com>, Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: make btrfs_dirty_inode() to always reserve metadata space
Date: Fri, 19 Feb 2021 08:31:08 +0800 [thread overview]
Message-ID: <0cf1604e-f54e-69ce-23e6-b043e975cbf4@gmx.com> (raw)
In-Reply-To: <6bc8bef5-43a0-f6c6-9b43-2f62a3e4e051@toxicpanda.com>
On 2021/2/19 上午12:14, Josef Bacik wrote:
> On 1/8/21 12:36 AM, Qu Wenruo wrote:
>> There are several qgroup flush related bugs fixed recently, all of them
>> are caused by the fact that we can trigger qgroup metadata space
>> reservation holding a transaction handle.
>>
>> Thankfully the only situation to trigger above reservation is
>> btrfs_dirty_inode().
>>
>> Currently btrfs_dirty_inode() will try join transactio first, then
>> update the inode.
>> If btrfs_update_inode() fails with -ENOSPC, then it retry to start
>> transaction to reserve metadata space.
>>
>> This not only forces us to reserve metadata space with a transaction
>> handle hold, but can't handle other errors like -EDQUOT.
>>
>> This patch will make btrfs_dirty_inode() to call
>> btrfs_start_transaction() directly without first try joining then
>> starting, so that in try_flush_qgroup() we won't hold a trans handle.
>>
>> This will slow down btrfs_dirty_inode() but my fstests doesn't show too
>> much different for most test cases, thus it may be worthy to skip such
>> performance "optimization".
>>
>> Signed-off-by: Qu Wenruo <wqu@suse.com>
>
> I'm not interested in slowing down the !qgroups case just for qgroups.
> We want to short circuit the start here because it has the potential to
> be _very_ expensive, when we may very well have space already allocated
> for the inode.
>
> The best solution I can think of for this is to add a bool to indicate
> that we don't want to attempt to make reservations.
The root problem here is, btrfs_dirty_inode() itself is an odd ball by
itself.
All other call sites are either reserving its metadata space by
btrfs_start_transaction(), or reserve metadata manually like delalloc.
Only btrfs_dirty_inode() is using join transaction and put all the
reserve logical into btrfs_delayed_inode_reserve_metadata().
> The only problem
> here is if the inode doesn't have space allocated for it, if it doesn't
> we need to fall back anyway. The speed up comes from inodes that
> already have the delayed inode setup. So simply tell it to error out if
> we're not already set up, and then we can fail back to
> btrfs_start_transaction(). That'll keep us in line with our performance
> for !qgroups and solve your qgroup related deadlock problems. Thanks,
Can't we do the check earlier? Like before we start or join transaction?
I really hate to do all the error out check deep in
btrfs_delayed_inode_reserve_metadata().
Thanks,
Qu
>
> Josef
prev parent reply other threads:[~2021-02-19 0:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 5:36 [PATCH] btrfs: make btrfs_dirty_inode() to always reserve metadata space Qu Wenruo
2021-01-12 12:19 ` Nikolay Borisov
2021-01-12 12:29 ` Qu Wenruo
2021-01-12 15:24 ` [btrfs] e86bb85b1f: stress-ng.utime.ops_per_sec -70.1% regression kernel test robot
2021-01-13 7:15 ` Qu Wenruo
2021-02-18 15:28 ` [PATCH] btrfs: make btrfs_dirty_inode() to always reserve metadata space Nikolay Borisov
2021-02-19 0:19 ` Qu Wenruo
2021-02-18 16:14 ` Josef Bacik
2021-02-19 0:31 ` 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=0cf1604e-f54e-69ce-23e6-b043e975cbf4@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.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