From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: dsterba@suse.cz, Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Add comment for BTRFS_ROOT_REF_COWS
Date: Mon, 17 Feb 2020 15:06:49 +0800 [thread overview]
Message-ID: <54ffe5f9-19d1-f916-04fa-3eceedc5aca7@gmx.com> (raw)
In-Reply-To: <20200214165334.GC2902@twin.jikos.cz>
[-- Attachment #1.1: Type: text/plain, Size: 2292 bytes --]
On 2020/2/15 上午12:53, David Sterba wrote:
> On Wed, Feb 12, 2020 at 03:46:51PM +0800, Qu Wenruo wrote:
>> This bit is being used in too many locations while there is still no
>> good enough explaination for how this bit is used.
>>
>> Not to mention its name really doesn't make much sense.
>>
>> So this patch will add my explanation on this bit, considering only
>> subvolume trees, along with its reloc trees have this bit, to me it
>> looks like this bit shows whether tree blocks of a root can be shared.
>
> I think there's more tan just sharing, it should say something about
> reference counted sharing. See eg. btrfs_block_can_be_shared:
>
> 864 /*
> 865 * Tree blocks not in reference counted trees and tree roots
> 866 * are never shared. If a block was allocated after the last
> 867 * snapshot and the block was not allocated by tree relocation,
> 868 * we know the block is not shared.
> 869 */
>
> And there can be more specialities found when grepping for REF_COWS. The
> comment explaination should be complete or at least mention what's not
> documenting. The I find the suggested version insufficient but don't
> have a concrete suggestions for improvement. By reading the comment and
> going through code I don't feel any wiser.
>
I see nothing extra conflicting the "shared tree blocks" part from
btrfs_block_can_be_shared().
In fact, reloc tree can only be created for trees with REF_COW bit.
For tree without that bit, we go a completely different way to relocate
them, by just cowing the path (aka the cowonly bit in build_backref_tree()).
if (root) {
if (test_bit(BTRFS_ROOT_REF_COWS, &root->state)) {
BUG_ON(node->new_bytenr);
BUG_ON(!list_empty(&node->list));
btrfs_record_root_in_trans(trans, root);
root = root->reloc_root;
node->new_bytenr = root->node->start;
node->root = root;
list_add_tail(&node->list, &rc->backref_cache.changed);
} else {
path->lowest_level = node->level;
ret = btrfs_search_slot(trans, root, key, path, 0, 1); <<<
btrfs_release_path(path);
if (ret > 0)
ret = 0;
}
So the "REF_COW means tree blocks can be shared" still looks pretty
valid to me.
Thanks,
Qu
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
next prev parent reply other threads:[~2020-02-17 7:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 7:46 [PATCH] btrfs: Add comment for BTRFS_ROOT_REF_COWS Qu Wenruo
2020-02-12 13:04 ` Josef Bacik
2020-02-14 16:53 ` David Sterba
2020-02-17 7:06 ` Qu Wenruo [this message]
2020-05-11 8:09 ` Qu Wenruo
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=54ffe5f9-19d1-f916-04fa-3eceedc5aca7@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dsterba@suse.cz \
--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