From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: damenly.su@gmail.com, linux-btrfs@vger.kernel.org
Cc: Su Yue <Damenly_Su@gmx.com>
Subject: Re: [PATCH 04/10] btrfs-progs: reform the function block_group_cache_tree_search()
Date: Thu, 5 Dec 2019 15:38:46 +0800 [thread overview]
Message-ID: <d491f547-626d-c974-8e70-9e39815a7dab@gmx.com> (raw)
In-Reply-To: <20191205042921.25316-5-Damenly_Su@gmx.com>
[-- Attachment #1.1: Type: text/plain, Size: 2744 bytes --]
On 2019/12/5 下午12:29, damenly.su@gmail.com wrote:
> From: Su Yue <Damenly_Su@gmx.com>
>
> Add the new value 2 of @contains in block_group_cache_tree_search().
> The new values means the function will return the block group that
> contains bytenr, otherwise return the next one that starts after
> @bytenr. Will be used in later commit.
>
> Signed-off-by: Su Yue <Damenly_Su@gmx.com>
> ---
> extent-tree.c | 20 +++++++++++++++-----
> 1 file changed, 15 insertions(+), 5 deletions(-)
>
> diff --git a/extent-tree.c b/extent-tree.c
> index ab576f8732a2..1d8535049eaf 100644
> --- a/extent-tree.c
> +++ b/extent-tree.c
> @@ -196,13 +196,16 @@ static int btrfs_add_block_group_cache(struct btrfs_fs_info *info,
> }
>
> /*
> - * This will return the block group at or after bytenr if contains is 0, else
> - * it will return the block group that contains the bytenr
> + * @contains:
> + * if 0, return the block group at or after bytenr if contains is 0.
> + * if 1, return the block group that contains the bytenr.
> + * if 2, return the block group that contains bytenr, otherwise return the
> + * next one that starts after @bytenr.
Thats a creative solution, good job on that.
However since contains is no longer just simple 1 or 0, it's better to
enum to define the behavior, other than using the immediate numbers.
> */
> static struct btrfs_block_group_cache *block_group_cache_tree_search(
> struct btrfs_fs_info *info, u64 bytenr, int contains)
> {
> - struct btrfs_block_group_cache *cache, *ret = NULL;
> + struct btrfs_block_group_cache *cache, *ret = NULL, *tmp = NULL;
> struct rb_node *n;
> u64 end, start;
>
> @@ -215,8 +218,8 @@ static struct btrfs_block_group_cache *block_group_cache_tree_search(
> start = cache->key.objectid;
>
> if (bytenr < start) {
> - if (!contains && (!ret || start < ret->key.objectid))
> - ret = cache;
> + if (!tmp || start < tmp->key.objectid)
> + tmp = cache;
This doesn't look correct.
I was expecting something based on last found node, other than doing
something strange in the rb-tree iteration code.
At least this breaks readability. It would be much better to handle this
after the rb tree while loop.
Thanks,
Qu
> n = n->rb_left;
> } else if (bytenr > start) {
> if (contains && bytenr <= end) {
> @@ -229,6 +232,13 @@ static struct btrfs_block_group_cache *block_group_cache_tree_search(
> break;
> }
> }
> +
> + /*
> + * If ret is NULL, means not found any block group cotanins @bytenr.
> + * So just except the case that cotanins equals 1.
> + */
> + if (!ret && contains != 1)
> + ret = tmp;
> return ret;
> }
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
next prev parent reply other threads:[~2019-12-05 7:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 4:29 [PATCH 00/10] unify origanization structure of block group cache damenly.su
2019-12-05 4:29 ` [PATCH 01/10] btrfs-progs: handle error if btrfs_write_one_block_group() failed damenly.su
2019-12-05 7:21 ` Qu Wenruo
2019-12-05 4:29 ` [PATCH 02/10] btrfs-progs: block_group: add rb tree related memebers damenly.su
2019-12-05 7:22 ` Qu Wenruo
2019-12-05 4:29 ` [PATCH 03/10] btrfs-progs: port block group cache tree insertion and lookup functions damenly.su
2019-12-05 7:29 ` Qu Wenruo
2019-12-05 8:32 ` Su Yue
2019-12-05 13:41 ` David Sterba
2019-12-05 4:29 ` [PATCH 04/10] btrfs-progs: reform the function block_group_cache_tree_search() damenly.su
2019-12-05 7:38 ` Qu Wenruo [this message]
2019-12-05 8:08 ` Su Yue
2019-12-05 4:29 ` [PATCH 05/10] btrfs-progs: adjust function btrfs_lookup_first_block_group_kernel damenly.su
2019-12-05 7:40 ` Qu Wenruo
2019-12-05 8:20 ` Su Yue
2019-12-05 4:29 ` [PATCH 06/10] btrfs-progs: abstract function btrfs_add_block_group_cache() damenly.su
2019-12-05 7:42 ` Qu Wenruo
2019-12-05 4:29 ` [PATCH 07/10] block-progs: block_group: add dirty_bgs list related memebers damenly.su
2019-12-05 7:43 ` Qu Wenruo
2019-12-05 4:29 ` [PATCH 08/10] btrfs-progs: pass @trans to functions touch dirty block groups damenly.su
2019-12-05 7:44 ` Qu Wenruo
2019-12-05 4:29 ` [PATCH 09/10] btrfs-progs: refrom block groups caches structure damenly.su
2019-12-05 7:51 ` Qu Wenruo
2019-12-05 8:09 ` Su Yue
2019-12-05 4:29 ` [PATCH 10/10] btrfs-progs: cleanups after block group cache reform damenly.su
2019-12-05 7:52 ` 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=d491f547-626d-c974-8e70-9e39815a7dab@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=Damenly_Su@gmx.com \
--cc=damenly.su@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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