From: Miao Xie <miaox@cn.fujitsu.com>
To: Chris Mason <chris.mason@oracle.com>,
Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 2/2] btrfs: Switching the extent buffer rbtree into a unlock radix tree
Date: Wed, 13 Oct 2010 10:17:22 +0800 [thread overview]
Message-ID: <4CB516B2.10809@cn.fujitsu.com> (raw)
In-Reply-To: <20101012184323.GU22691@think>
On Tue, 12 Oct 2010 14:43:23 -0400, Chris Mason wrote:
> On Tue, Oct 12, 2010 at 05:43:14PM +0800, Miao Xie wrote:
>> This patch reduces the CPU time spent in the extent buffer search by using the
>> radix tree instead of the rbtree and using the rcu lock instead of the spin
>> lock.
>>
>> I did a quick test by the benchmark tool[1] and found the patch improve the
>> file creation/deletion performance problem that I have reported[2].
>
> Thanks, this is much smaller than I expected. I'll hammer on it here.
By the way, I found we had 16T limit on 32-bits machines, because the page cache
of 32-bits machines can only manage 16T data, and the btrfs metadata is cached
in the page cache.
Regards
Miao
prev parent reply other threads:[~2010-10-13 2:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 9:43 [PATCH 2/2] btrfs: Switching the extent buffer rbtree into a unlock radix tree Miao Xie
2010-10-12 18:43 ` Chris Mason
2010-10-13 2:17 ` Miao Xie [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=4CB516B2.10809@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=chris.mason@oracle.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;
as well as URLs for NNTP newsgroup(s).