From: Chris Mason <chris.mason@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Btrfs changes for 2.6.30-rc
Date: Tue, 21 Apr 2009 09:29:05 -0400 [thread overview]
Message-ID: <1240320545.4869.22.camel@think.oraclecorp.com> (raw)
Hello everyone,
The master branch of:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git
Has some fixes for oopsen and a cluster of bugs inside of one of the
btree readahead functions.
I also jumped on the fsync latency train for btrfs and switched over to
WRITE_SYNC for the writes I was going to wait on.
This is a bigger change in btrfs because I had to add a high priority
list to the async helper threads, but it had a big impact on performance
overall. Before, the writes we were waiting on would get stuck behind
the less critical writes in the async helper threads, and now they pop
out much faster.
Average fsync latencies concurrent with a streaming writer went down
from ~5 seconds (with longer peaks) to < 1 second.
Chris Mason (4):
Btrfs: use WRITE_SYNC for synchronous writes
Btrfs: add a priority queue to the async thread helpers
Btrfs: fix oops on page->mapping->host during writepage
Btrfs: use the right node in reada_for_balance
fs/btrfs/async-thread.c | 60 ++++++++++++++++++-----
fs/btrfs/async-thread.h | 2
fs/btrfs/ctree.c | 17 ++++--
fs/btrfs/disk-io.c | 9 ++-
fs/btrfs/extent_io.c | 86 ++++++++++++++++++++++++---------
fs/btrfs/file.c | 2
fs/btrfs/ordered-data.c | 2
fs/btrfs/volumes.c | 124 +++++++++++++++++++++++++++++++++++++-----------
fs/btrfs/volumes.h | 13 ++++-
-chris
next reply other threads:[~2009-04-21 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 13:29 Chris Mason [this message]
2009-04-21 17:02 ` [GIT PULL] Btrfs changes for 2.6.30-rc Chris Mason
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=1240320545.4869.22.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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