From: Dan Williams <dan.j.williams@intel.com>
To: neilb@suse.de, raziebe@gmail.com
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/2] An evolutionary change to the raid456 queuing model
Date: Wed, 27 Jun 2007 12:09:23 -0700 [thread overview]
Message-ID: <20070627190534.5685.34447.stgit@dwillia2-linux.ch.intel.com> (raw)
Raz's stripe-deadline patch illuminated the fact that the current
queuing model leaves write performance on the table in some cases. The
following patches introduce a new queuing model which attempts to
recover this performance.
On an ARM based iop13xx platform I see an averaged %14.7 increase in
throughput as reported by the following simple test:
for i in `seq 1 10`; do dd if=/dev/zero of=/dev/md0 bs=1024k count=512; done
This was performed on a default configured 4-disk SATA array (chunksize=64k
stripe_cache_size=256)
However, a test with an ext2 filesystem and tiobench showed negligible
changes. My suspicion is that the new queuing model, as it currently stands,
can extract some more performance when full stripe writes are present, but in
the tiobench case there is not enough to take advantage of the queue's preread
prevention logic (improving this case is the goal of releasing this version of
the patches).
These patches are on top of the md-accel series. I will spin a complete
set based on 2.6.22 once it goes final (2.6.22-iop1 to be released on
SourceForge). Until then the complete series is available via git:
git://lost.foo-projects.org/~dwillia2/git/iop md-accel+experimental
Not to be confused with the acceleration patch set released yesterday which is
targetted at 2.6.23. These queuing changes need some more time to cook.
--
Dan
next reply other threads:[~2007-06-27 19:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 19:09 Dan Williams [this message]
2007-06-27 19:09 ` [RFC PATCH 1/2] raid5: add the stripe_queue object for tracking raid io requests Dan Williams
2007-06-27 19:09 ` [RFC PATCH 2/2] raid5: use stripe_queues to prioritize the "most deserving" requests 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=20070627190534.5685.34447.stgit@dwillia2-linux.ch.intel.com \
--to=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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).