From: "Dan Williams" <dan.j.williams@intel.com>
To: NeilBrown <neilb@suse.de>, "Jeff Garzik" <jeff@garzik.org>,
"Chris Leech" <christopher.leech@intel.com>,
akpm@osdl.org
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>,
"Linux RAID Mailing List" <linux-raid@vger.kernel.org>,
"Olof Johansson" <olof@lixom.net>
Subject: [PATCH 00/12] md raid acceleration and the async_tx api
Date: Thu, 30 Nov 2006 12:55:46 -0700 [thread overview]
Message-ID: <e9c3a7c20611301155p4069c642j276d7705b0f81447@mail.gmail.com> (raw)
Here is the latest version of the raid acceleration patch set. Since
the last release I have created the async_tx api to address the
concerns raised by Neil and Jeff. With this api in place the raid5
asynchronous and synchronous paths are no longer separated, i.e. there
are no hardware specific concerns in the raid code.
The async_tx api is proposed as a special dmaengine management client
that allows offload engines to be used for bulk memory
transfers/transforms, and fallback to synchronous routines when an
engine is not present.
This implementation has been tested on iop13xx and iop33x platforms in
both the synchronous case and the asynchronous case with the iop-adma
driver. The changes to the ioatdma driver have only been compile
tested, and testing NET_DMA with iop-adma is pending.
Please consider for -mm. These patches are against 2.6.19.
Dan Williams:
dmaengine: add base support for the async_tx api
dmaengine: add the async_tx api
dmaengine: driver for the iop32x, iop33x, and iop13xx raid engines
md: add raid5_run_ops and support routines
md: workqueue for raid5 operations
md: move write operations to raid5_run_ops
md: move raid5 compute block operations to raid5_run_ops
md: move raid5 parity checks to raid5_run_ops
md: satisfy raid5 read requests via raid5_run_ops
md: use async_tx and raid5_run_ops for raid5 expansion operations
md: raid5 io requests to raid5_run_ops
md: remove raid5 compute_block and compute_parity5
Regards,
Dan
next reply other threads:[~2006-11-30 19:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 19:55 Dan Williams [this message]
2006-11-30 20:10 ` [PATCH 01/12] dmaengine: add base support for " Dan Williams
2006-11-30 20:10 ` [PATCH 02/12] dmaengine: add " Dan Williams
2006-12-01 1:19 ` Dan Williams
2006-11-30 20:10 ` [PATCH 03/12] dmaengine: driver for the iop32x, iop33x, and iop13xx raid engines Dan Williams
2006-11-30 20:10 ` [PATCH 04/12] md: add raid5_run_ops and support routines Dan Williams
2006-11-30 20:10 ` [PATCH 05/12] md: workqueue for raid5 operations Dan Williams
2006-11-30 20:10 ` [PATCH 06/12] md: move write operations to raid5_run_ops Dan Williams
2006-11-30 20:10 ` [PATCH 07/12] md: move raid5 compute block " Dan Williams
2006-11-30 20:10 ` [PATCH 08/12] md: move raid5 parity checks " Dan Williams
2006-11-30 20:10 ` [PATCH 09/12] md: satisfy raid5 read requests via raid5_run_ops Dan Williams
2006-11-30 20:10 ` [PATCH 10/12] md: use async_tx and raid5_run_ops for raid5 expansion operations Dan Williams
2006-11-30 20:10 ` [PATCH 11/12] md: raid5 io requests to raid5_run_ops Dan Williams
2006-11-30 20:11 ` [PATCH 12/12] md: remove raid5 compute_block and compute_parity5 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=e9c3a7c20611301155p4069c642j276d7705b0f81447@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=akpm@osdl.org \
--cc=christopher.leech@intel.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=olof@lixom.net \
/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
all inboxes | Powered by JetHome®