From: Chris Mason <chris.mason@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: Multi-device update
Date: Wed, 16 Apr 2008 11:34:19 -0400 [thread overview]
Message-ID: <200804161134.19237.chris.mason@oracle.com> (raw)
Hello everyone,
I've pushed out another set of changes to the unstable trees, and these
include:
* RAID 1+0 support
mkfs.btrfs -d raid10 -m raid10 /dev/sd...
4 or more drives required.
* async work queues for checksumming writes
* Better back references in the multi-device data structs
The async work queues include code to checksum data pages without the FS mutex
held, greatly increasing streaming write throughput. On my 4 drive system, I
was getting around 120MB/s writes with checksumming on. Now I get 180MB/s,
which is disk speed.
The rest of the week will be spent doing hot add/remove of devices. Happy
testing ;)
-chris
next reply other threads:[~2008-04-16 15:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 15:34 Chris Mason [this message]
2008-04-16 16:14 ` Multi-device update Andi Kleen
2008-04-16 16:54 ` Chris Mason
2008-04-16 17:43 ` Andi Kleen
2008-04-16 18:04 ` Chris Mason
2008-04-16 18:10 ` Andi Kleen
2008-04-16 18:14 ` Jens Axboe
2008-04-16 18:24 ` Andi Kleen
2008-04-16 18:26 ` Jens Axboe
2008-04-16 18:28 ` 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=200804161134.19237.chris.mason@oracle.com \
--to=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).