linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@gmail.com>
To: linux-raid@vger.kernel.org
Cc: dave.jiang@gmail.com
Subject: Accelerating Linux software raid
Date: Tue, 6 Sep 2005 11:24:24 -0700	[thread overview]
Message-ID: <e9c3a7c2050906112410dc1d16@mail.gmail.com> (raw)

Hello,

I am writing to the list to gauge interest for a modification of the
md driver that allows it to take advantage of raid acceleration
hardware.  I/O processors like the Intel IOP333
(http://www.intel.com/design/iio/docs/iop333.htm) contain an xor
engine for raid5 and raid6 calculations, but currently the md driver
does not fully utilize these resources.

Dave Jiang wrote a driver that re-routed calls to xor_block() to use
the hardware xor engine.  However, from my understating, he found that
performance did not improve, due to the fact that md deals in
PAGE_SIZE (4K) blocks.  At 4K the overhead of setting up the engine
destroys any performance advantage over a software xor.  The goal of
the modification would be to enable md to understand the capacity of
the platform's xor resources and allow it to issue optimal block
sizes.

The first question is whether a solution along these lines would be
valued by the community?  The effort is non-trivial.

Assuming a positive response I will solicit implementation ideas and
acceptance criteria from the list.

Thank you for your consideration,

Dan

             reply	other threads:[~2005-09-06 18:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06 18:24 Dan Williams [this message]
2005-09-06 21:52 ` Accelerating Linux software raid Molle Bestefich
2005-09-10  4:51 ` Mark Hahn
2005-09-10 12:58   ` Ric Wheeler
2005-09-10 15:35     ` Mark Hahn
2005-09-10 19:13       ` Dan Williams
2005-09-11  2:06       ` Ric Wheeler
2005-09-11  2:35         ` Konstantin Olchanski
2005-09-11 12:00           ` Ric Wheeler
2005-09-11 20:19             ` Mark Hahn
2005-09-10  8:35 ` Colonel Hell
2005-09-11 23:14 ` Neil Brown

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=e9c3a7c2050906112410dc1d16@mail.gmail.com \
    --to=dan.j.williams@gmail.com \
    --cc=dave.jiang@gmail.com \
    --cc=linux-raid@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).