From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Dan Williams <dan.j.williams@intel.com>
Cc: neilb@suse.de, akpm@linux-foundation.org,
christopher.leech@intel.com, linux-kernel@vger.kernel.org,
linux-raid@vger.kernel.org
Subject: Re: [PATCH 00/16] raid acceleration and asynchronous offload api for 2.6.22
Date: Wed, 02 May 2007 16:55:03 +1000 [thread overview]
Message-ID: <463835C7.3020902@yahoo.com.au> (raw)
In-Reply-To: <20070502060949.7066.357.stgit@dwillia2-linux.ch.intel.com>
Dan Williams wrote:
> I am pleased to release this latest spin of the raid acceleration
> patches for merge consideration. This release aims to address all
> pending review items including MD bug fixes and async_tx api changes
> from Neil, and concerns on channel management from Chris and others.
>
> Data integrity tests using home grown scripts and 'iozone -V' are
> passing. I am open to suggestions for additional testing criteria.
Do you have performance numbers?
--
SUSE Labs, Novell Inc.
next prev parent reply other threads:[~2007-05-02 6:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 6:14 [PATCH 00/16] raid acceleration and asynchronous offload api for 2.6.22 Dan Williams
2007-05-02 6:15 ` [PATCH 01/16] dmaengine: add base support for the async_tx api Dan Williams
2007-05-02 6:15 ` [PATCH 02/16] dmaengine: move channel management to the client Dan Williams
2007-05-02 6:16 ` [PATCH 03/16] ARM: Add drivers/dma to arch/arm/Kconfig Dan Williams
2007-05-02 6:16 ` [PATCH 04/16] dmaengine: add the async_tx api Dan Williams
2007-05-02 6:17 ` [PATCH 05/16] md: add raid5_run_ops and support routines Dan Williams
2007-05-02 6:17 ` [PATCH 06/16] md: use raid5_run_ops for stripe cache operations Dan Williams
2007-05-02 6:18 ` [PATCH 07/16] md: move write operations to raid5_run_ops Dan Williams
2007-05-02 6:18 ` [PATCH 08/16] md: move raid5 compute block " Dan Williams
2007-05-02 6:19 ` [PATCH 09/16] md: move raid5 parity checks " Dan Williams
2007-05-02 6:19 ` [PATCH 10/16] md: satisfy raid5 read requests via raid5_run_ops Dan Williams
2007-05-02 6:20 ` [PATCH 11/16] md: use async_tx and raid5_run_ops for raid5 expansion operations Dan Williams
2007-05-02 6:20 ` [PATCH 12/16] md: move raid5 io requests to raid5_run_ops Dan Williams
2007-05-02 6:21 ` [PATCH 13/16] md: remove raid5 compute_block and compute_parity5 Dan Williams
2007-05-02 6:21 ` [PATCH 14/16] dmaengine: driver for the iop32x, iop33x, and iop13xx raid engines Dan Williams
2007-05-02 6:22 ` [PATCH 15/16] iop13xx: Surface the iop13xx adma units to the iop-adma driver Dan Williams
2007-05-02 6:22 ` [PATCH 16/16] iop3xx: Surface the iop3xx DMA and AAU " Dan Williams
2007-05-02 6:55 ` Nick Piggin [this message]
2007-05-02 15:45 ` [PATCH 00/16] raid acceleration and asynchronous offload api for 2.6.22 Williams, Dan J
2007-05-02 15:55 ` Justin Piszcz
2007-05-02 16:17 ` Williams, Dan J
2007-05-02 16:19 ` Justin Piszcz
2007-05-02 16:36 ` Dagfinn Ilmari Mannsåker
2007-05-02 16:42 ` Williams, Dan J
-- strict thread matches above, loose matches on Subject: below --
2007-05-10 14:12 Tomasz Chmielewski
2007-05-10 15:32 ` Tomasz Chmielewski
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=463835C7.3020902@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@linux-foundation.org \
--cc=christopher.leech@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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