linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: neilb@suse.de
Cc: linux-raid@vger.kernel.org, yur@emcraft.com
Subject: [PATCH 0/8] Asynchronous raid6 acceleration (part 3 of 3)
Date: Wed, 03 Jun 2009 18:28:58 -0700	[thread overview]
Message-ID: <20090604012709.11507.15528.stgit@dwillia2-linux.ch.intel.com> (raw)

This series covers the changes to md/raid6 to use the new offload
capabilities of async_tx.  Part 1 [1] covered the changes to async_tx
for asynchronous raid6 parity generation and recovery.  Part 2 [2]
covered the updates to the iop-adma driver to enable raid6.

A merge of these 3 topic series is available via the raid6 branch of
async_tx.git:

	git://git.kernel.org/pub/scm/linux/kernel/git/djbw/async_tx.git raid6

The basic implementation of these patches have not changed much from
Yuri's previous release [3].  Instead this series has been rebased to
incorporate the modified async_tx/raid6 apis.  Note that the rework of
md/raid456 to move its async_tx parameter allocations from the stack to
the heap was included in commit 'md/raid5: add scribble region for
buffer lists' of Part 1 [4].  Current testing in the lab is passing, and
the code is ready for wider testing.

The 'raid6' branch will be placed in linux-next and if all goes well a
pull request may be sent towards the end of the 2.6.31 merge window.

Please review.

Thanks,
Dan

[1]: http://marc.info/?l=linux-raid&m=124269482227272&w=2
[2]: http://marc.info/?l=linux-raid&m=124293271625675&w=2
[3]: http://thread.gmane.org/gmane.linux.raid/21286
[4]: http://marc.info/?l=linux-raid&m=124269482227284&w=2

---

Dan Williams (3):
      md/raid6: asynchronous handle_parity_check6
      md/raid6: asynchronous raid6 operations
      md/raid5: factor out mark_uptodate from ops_complete_compute5

Yuri Tikhonov (5):
      md/raid6: remove synchronous infrastructure
      md/raid6: asynchronous handle_stripe6
      md/raid6: asynchronous handle_stripe_dirtying6
      md/raid6: asynchronous handle_stripe_fill6
      md/raid5,6: common schedule_reconstruction for raid5/6


 drivers/md/Kconfig |    2 
 drivers/md/raid5.c | 1139 +++++++++++++++++++++++++++++-----------------------
 drivers/md/raid5.h |    8 
 3 files changed, 645 insertions(+), 504 deletions(-)

             reply	other threads:[~2009-06-04  1:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04  1:28 Dan Williams [this message]
2009-06-04  1:29 ` [PATCH 1/8] md/raid5: factor out mark_uptodate from ops_complete_compute5 Dan Williams
2009-06-04  1:29 ` [PATCH 2/8] md/raid6: asynchronous raid6 operations Dan Williams
2009-06-04  6:33   ` Neil Brown
2009-06-04  1:29 ` [PATCH 3/8] md/raid5,6: common schedule_reconstruction for raid5/6 Dan Williams
2009-06-04  1:29 ` [PATCH 4/8] md/raid6: asynchronous handle_stripe_fill6 Dan Williams
2009-06-04  6:37   ` Neil Brown
2009-06-04  1:29 ` [PATCH 5/8] md/raid6: asynchronous handle_stripe_dirtying6 Dan Williams
2009-06-04  1:29 ` [PATCH 6/8] md/raid6: asynchronous handle_parity_check6 Dan Williams
2009-06-04  1:29 ` [PATCH 7/8] md/raid6: asynchronous handle_stripe6 Dan Williams
2009-06-04  1:29 ` [PATCH 8/8] md/raid6: remove synchronous infrastructure 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=20090604012709.11507.15528.stgit@dwillia2-linux.ch.intel.com \
    --to=dan.j.williams@intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=yur@emcraft.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).