From: "Dan Williams" <dan.j.williams@intel.com>
To: linux-raid maillist <linux-raid@vger.kernel.org>
Cc: Neil Brown <neilb@suse.de>,
"Raz Ben-Jehuda(caro)" <raziebe@gmail.com>,
Bill Davidsen <davidsen@tmr.com>
Subject: [RFT] 2.6.22.1-iop1 for improved sequential write performance (stripe-queue)
Date: Thu, 19 Jul 2007 17:17:36 -0700 [thread overview]
Message-ID: <e9c3a7c20707191717s4809eab1s4966f7e0c21c6424@mail.gmail.com> (raw)
Per Bill Davidsen's request I have made available a 2.6.22.1 based
kernel with the current raid5 performance changes I have been working
on:
1/ Offload engine acceleration (recently merged for the 2.6.23
development cycle)
2/ Stripe-queue, an evolutionary change to the raid5 queuing model (take4)
The offload engine work only helps platforms with offload engines and
should not affect performance otherwise. The stripe-queue work is an
attempt to increase sequential write performance and should benefit
most platforms.
The patch series is available on the Xscale(r) IOP SourceForge page:
http://downloads.sourceforge.net/xscaleiop/patches-2.6.22.1-iop1-x86fix.tar.gz
Use quilt to apply the series on top of a fresh 2.6.22.1 source tree:
$ wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.22.1.tar.bz2
$ tar xjf linux-2.6.22.1.tar.bz2
$ cd linux-2.6.22.1
$ tar xzvf patches-2.6.22.1-iop1.tar.gz
$ cp patches/series.x86 patches/series
$ quilt push -a
Configure and build the kernel as normal, there are no configuration
options for stripe-queue.
Any feedback, bug report, fix, or suggestion is welcome.
Thanks,
Dan
next reply other threads:[~2007-07-20 0:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 0:17 Dan Williams [this message]
2007-08-04 17:54 ` [RFT] 2.6.22.1-iop1 for improved sequential write performance (stripe-queue) Mr. James W. Laferriere
2007-08-06 21:59 ` Dan Williams
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=e9c3a7c20707191717s4809eab1s4966f7e0c21c6424@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=raziebe@gmail.com \
/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).