From: Chris Mason <chris.mason@oracle.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: New compression fixes pushed out
Date: Thu, 06 Nov 2008 22:16:03 -0500 [thread overview]
Message-ID: <1226027763.15281.32.camel@think.oraclecorp.com> (raw)
Hello,
I've pushed out my current batch of fixes for the compression code. It
introduces async compression for writes and does a better job of filling
in pages for compressed extents while reading it.
The latest git trees should fix the bad page mapping errors and improve
performance even for uncompressed writes.
Checksumming is now done via an ordered work queue, which makes sure IO
is sent down to the device in the same order the writes were started.
On my 4 drive array, it pushes performance from 280MB/s 340MB/s for
sequential writes.
The same ordered work queues are used to keep ordering sane for the
async compression code.
-chris
reply other threads:[~2008-11-07 3:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1226027763.15281.32.camel@think.oraclecorp.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