From: Josef Bacik <jbacik@fb.com>
To: Wang Shilong <wangshilong1991@gmail.com>
Cc: Wang Shilong <wangsl.fnst@cn.fujitsu.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] Btrfs: rework ulist with list+rb_tree
Date: Tue, 28 Jan 2014 11:08:16 -0500 [thread overview]
Message-ID: <52E7D5F0.9030707@fb.com> (raw)
In-Reply-To: <38D3E1F0-3519-4EF1-9B78-A872371B3284@gmail.com>
On 01/28/2014 11:03 AM, Wang Shilong wrote:
> Hello Josef,
>
>> On 01/27/2014 04:59 AM, Wang Shilong wrote:
>>> We are really suffering from now ulist's implementation, some developers
>>> gave their try, and i just gave some of my ideas for things:
>>>
>>> 1. use list+rb_tree instead of arrary+rb_tree
>>>
>>> 2. add cur_list to iterator rather than ulist structure.
>>>
>>> 3. add seqnum into every node when they are added, this is
>>> used to do selfcheck when iterating node.
>>>
>>> I noticed Zach Brown's comments before, long term is to kick off
>>> ulist implementation, however, for now, we need at least avoid
>>> arrary from ulist.
>>>
>>> Cc: Liu Bo <bo.li.liu@oracle.com>
>>> Cc: Josef Bacik <jbacik@fb.com>
>>> Cc: Zach Brown <zab@redhat.com>
>>> Signed-off-by: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
>>> ---
>>> v2->v3:
>>> only do selfchecks with CONFIG_BTRFS_DEBUG enabled(Thanks to Josef!)
>>> update ulist's comments since they are out of date.
>>> v1->v2:
>>> add RFC title since this patch needs more reviews and comments.
>>> fix a used after free bug in ulist_fini().
>> I like the patch but it doesn't build since things like qgroups rely on ulist->nnodes. You need to fix that in your patch and make sure this stuff compiles. Thanks,
> Sorry about if it did not compile.
>
> but I really compiled and tested it in my box, did you apply your qgroup patches?
> This patch is based on btrfs-next without your previous qgroup patches.
>
> Anyway i will double check it…..
>
Yeah I thought I was doing something wrong but I'm definitely on my
master branch which doesn't have my qgroup patches in it. If it's still
working for you now just wait a bit for me to push out this next update
and rebase onto it and resend. Thanks,
Josef
next prev parent reply other threads:[~2014-01-28 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 9:59 [PATCH v3 1/2] Btrfs: rework ulist with list+rb_tree Wang Shilong
2014-01-27 9:59 ` [PATCH v3 2/2] Btrfs: do not export ulist functions Wang Shilong
2014-01-27 16:30 ` David Sterba
2014-01-27 9:59 ` [PATCH] Btrfs: allocate ulist with a slab allocator Wang Shilong
2014-01-27 16:39 ` David Sterba
2014-01-28 15:53 ` [PATCH v3 1/2] Btrfs: rework ulist with list+rb_tree Josef Bacik
2014-01-28 16:03 ` Wang Shilong
2014-01-28 16:08 ` Josef Bacik [this message]
2014-01-28 16:21 ` Wang Shilong
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=52E7D5F0.9030707@fb.com \
--to=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangshilong1991@gmail.com \
--cc=wangsl.fnst@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.