From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Diego Calleja <diegocg@gmail.com>, Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: extent-tree: Add comment for walk_control to explain how btrfs drops a subvolume.
Date: Thu, 25 Jul 2019 06:55:38 +0800 [thread overview]
Message-ID: <dd9d30cc-21d7-d216-da5f-024bdca360b6@gmx.com> (raw)
In-Reply-To: <3769531.JR3RUOJnLt@archlinux>
[-- Attachment #1.1: Type: text/plain, Size: 609 bytes --]
On 2019/7/25 上午6:25, Diego Calleja wrote:
> El martes, 23 de julio de 2019 9:57:21 (CEST) Qu Wenruo escribió:
>> + * A <- tree root, level 2
>> + * / \
>> + * B C <- tree nodes, level 1
>> + * / \ / \
>> + * D E F G <- tree leaves, level 0
>> + *
>> + * 1) Basic dropping.
>> + * All above tree blocks are owned exclusively.
>> + * Drop tree blocks using LRN iteration.
>> + * Tree drop sequence is: D E B F C G A.
>
> Excuse me if I am wrong, but there seems to be a small typo, shouldn't
> it be "F G C"?
My bad, nice catch!
Thanks,
Qu
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-07-24 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 7:57 [PATCH] btrfs: extent-tree: Add comment for walk_control to explain how btrfs drops a subvolume Qu Wenruo
2019-07-24 22:25 ` Diego Calleja
2019-07-24 22:55 ` 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=dd9d30cc-21d7-d216-da5f-024bdca360b6@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=diegocg@gmail.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