From: Arne Jansen <sensille@gmx.net>
To: chris.mason@oracle.com, linux-btrfs@vger.kernel.org
Subject: [PATCH v5 0/7] btrfs: generic readeahead interface
Date: Fri, 1 Jul 2011 22:58:46 +0200 [thread overview]
Message-ID: <cover.1309553533.git.sensille@gmx.net> (raw)
This series introduces a generic readahead interface for btrfs trees.
The intention is to use it to speed up scrub in a first run, but balance
is another hot candidate. In general, every tree walk could be accompanied
by a readahead. Deletion of large files comes to mind, where the fetching
of the csums takes most of the time.
Also the initial build-ups of free-space-caches and inode-allocator-caches
could be sped up.
To make testing easier, a simple ioctl interface is added to trigger a read-
ahead from user mode. It also implements a tree walk in the traditional way.
A simple demonstration from my 7-disk test btrfs:
- enumerating the extent tree (traditional): 351s
- enumerating the extent tree (readahead): 41s
- enumerating extents+csum tree (readahead): 49s
The implementation is also tested with this tool in various combinations of
parallel reads of the same and of different trees.
The main changes from v1 are:
- Switch from extent_state flags to extent_buffer flags.
- Fix a race when triggering the read.
- Fix a bug where only parts of the requested range where actually prefetched.
The hit only when requesting parts of a tree, so the above numbers doesn't
change.
Change from v2:
- use rcu instead of transaction to protect root->node
Changes from v3:
- rebased to current for-linus
- in v3 patch 1 was missing
Changes from v4:
- adoptions according the Josef's review. See the parts for more detailed
comments
This series is also available at
git://git.kernel.org/pub/scm/linux/kernel/git/arne/btrfs-unstable-arne.git readahead
Arne Jansen (7):
btrfs: add an extra wait mode to read_extent_buffer_pages
btrfs: add READAHEAD extent buffer flag
btrfs: state information for readahead
btrfs: initial readahead code and prototypes
btrfs: hooks for readahead
btrfs: test ioctl for readahead
btrfs: use readahead API for scrub
fs/btrfs/Makefile | 3 +-
fs/btrfs/ctree.h | 21 ++
fs/btrfs/disk-io.c | 85 +++++-
fs/btrfs/disk-io.h | 2 +
fs/btrfs/extent_io.c | 9 +-
fs/btrfs/extent_io.h | 4 +
fs/btrfs/ioctl.c | 93 +++++-
fs/btrfs/ioctl.h | 16 +
fs/btrfs/reada.c | 949 ++++++++++++++++++++++++++++++++++++++++++++++++++
fs/btrfs/scrub.c | 116 +++----
fs/btrfs/volumes.c | 8 +
fs/btrfs/volumes.h | 8 +
12 files changed, 1239 insertions(+), 75 deletions(-)
create mode 100644 fs/btrfs/reada.c
--
1.7.3.4
next reply other threads:[~2011-07-01 20:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 20:58 Arne Jansen [this message]
2011-07-01 20:58 ` [PATCH v5 1/7] btrfs: add an extra wait mode to read_extent_buffer_pages Arne Jansen
2011-07-20 16:42 ` [PATCH v6] " Arne Jansen
2011-07-01 20:58 ` [PATCH v5 2/7] btrfs: add READAHEAD extent buffer flag Arne Jansen
2011-07-01 20:58 ` [PATCH v5 3/7] btrfs: state information for readahead Arne Jansen
2011-07-01 20:58 ` [PATCH v5 4/7] btrfs: initial readahead code and prototypes Arne Jansen
2011-07-01 20:58 ` [PATCH v5 5/7] btrfs: hooks for readahead Arne Jansen
2011-07-01 20:58 ` [PATCH v5 6/7] btrfs: test ioctl " Arne Jansen
2011-07-01 20:58 ` [PATCH v5 7/7] btrfs: use readahead API for scrub Arne Jansen
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=cover.1309553533.git.sensille@gmx.net \
--to=sensille@gmx.net \
--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).