From: Miao Xie <miaox@cn.fujitsu.com>
To: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [RFC][PATCH V2 0/4] Btrfs: introduce extent buffer cache to btrfs
Date: Tue, 09 Oct 2012 15:32:45 +0800 [thread overview]
Message-ID: <5073D31D.6050805@cn.fujitsu.com> (raw)
In-Reply-To: <5062E563.7090105@cn.fujitsu.com>
Any comment？
On wed, 26 Sep 2012 19:22:11 +0800, Miao Xie wrote:
> This patchset introduce extent buffer cache to btrfs. The basic idea
> is to reduce the search time and the contentions of the extent buffer
> lock by re-using the last search result.
>
> I ran stress.sh, xfstests and some other tools to test it, all of them
> worked well.
>
> As a performance improvement patchset, of course we did performance test.
> Because this patchset is to improve the b+ tree search, in other words,
> it improves the performance of the metadata operations, we use file creation
> test to measure it. So we ran 10 tasks, and all of them created 100000 files
> in their own directories at the same time. As the result, we found this patchset
> makes btrfs ~20% faster(98s -> 77s).
>
> we can pull this patchset from the URL
>
> git://github.com/miaoxie/linux-btrfs.git extent-buffer-cache
>
> Thanks
> Miao
> ---
> Miao Xie (4):
> Btrfs: restructure btrfs_search_slot()
> Btrfs: introduce extent buffer cache for each i-node
> Btrfs: introduce extent buffer cache for delayed inode
> Btrfs: introduce extent buffer cache for delayed reference
>
> fs/btrfs/acl.c | 1 -
> fs/btrfs/btrfs_inode.h | 6 +-
> fs/btrfs/compression.c | 1 -
> fs/btrfs/ctree.c | 598 ++++++++++++++++++++++++++++++++++++---------
> fs/btrfs/ctree.h | 32 +++-
> fs/btrfs/delayed-inode.c | 23 ++
> fs/btrfs/dir-item.c | 2 +
> fs/btrfs/disk-io.c | 2 +-
> fs/btrfs/export.c | 1 -
> fs/btrfs/extent-tree.c | 6 +
> fs/btrfs/extent_io.c | 9 +-
> fs/btrfs/extent_io.h | 38 +++
> fs/btrfs/file-item.c | 4 +-
> fs/btrfs/file.c | 5 +-
> fs/btrfs/inode-item.c | 10 +-
> fs/btrfs/inode.c | 36 +++-
> fs/btrfs/ioctl.c | 1 -
> fs/btrfs/ordered-data.c | 1 -
> fs/btrfs/relocation.c | 1 -
> fs/btrfs/send.c | 1 -
> fs/btrfs/super.c | 1 -
> fs/btrfs/transaction.c | 11 +
> fs/btrfs/transaction.h | 4 +-
> fs/btrfs/tree-log.c | 6 +-
> fs/btrfs/xattr.c | 2 +-
> 25 files changed, 651 insertions(+), 151 deletions(-)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2012-10-09 7:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 11:22 [RFC][PATCH V2 0/4] Btrfs: introduce extent buffer cache to btrfs Miao Xie
2012-09-26 11:27 ` [RFC][PATCH V2 1/4] Btrfs: restructure btrfs_search_slot() Miao Xie
2012-09-26 11:37 ` [RFC][PATCH V2 2/4] Btrfs: introduce extent buffer cache for each i-node Miao Xie
2012-09-26 11:38 ` [RFC][PATCH V2 3/4] Btrfs: introduce extent buffer cache for delayed inode Miao Xie
2012-09-26 11:39 ` [RFC][PATCH V2 4/4] Btrfs: introduce extent buffer cache for delayed reference Miao Xie
2012-10-01 16:53 ` [RFC][PATCH V2 0/4] Btrfs: introduce extent buffer cache to btrfs Tim Chen
2012-10-09 7:32 ` 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=5073D31D.6050805@cn.fujitsu.com \
--to=miaox@cn.fujitsu.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).