From: NeilBrown <neilb@suse.de>
To: linux-raid@vger.kernel.org
Cc: Dan Williams <dan.j.williams@intel.com>
Subject: [md PATCH 00/11] Series short description
Date: Fri, 16 Oct 2009 16:49:17 +1100 [thread overview]
Message-ID: <20091016054316.24208.33818.stgit@notabene.brown> (raw)
Hi,
The following are a series of patches for 2.6.32-rc that I hope to
ask Linus to pull mid next week. They are already in my for-next tree.
Review always welcome.
Dan, I would particularly like you to check over
raid6/async_tx: handle holes in block list in async_syndrome_val
md/async: don't pass a memory pointer as a page pointer.
as they fix some issues with the recent conversion of raid6 to work
with async offload. Problems particularly occurred with 'ddf' style
layouts where there the Q syndrome is calculated over data blocks and
some 'zero' blocks.
My mdadm test suite now has some tests that test every single RAID5
and RAID6 layout and every combination of devices failing. And also
uses the new reshape functionality to transition an array through
each different layout. It has been very helpful at finding bugs.
One particularly important bug is that thought 2.6.31 can reshape a
RAID5 to have fewer devices, if the reshape is aborted in the middle,
2.6.31 cannot restart that reshape. With these patches 2.6.32 will
be able to. I suspect that when I release mdadm-3.1 it will refuse
to reduce the number of devices on kernels earlier than 2.6.32.
Thanks,
NeilBrown
---
Dan Williams (2):
md/raid456: downlevel multicore operations to raid_run_ops
md/raid5: initialize conf->device_lock earlier
NeilBrown (8):
raid6/async_tx: handle holes in block list in async_syndrome_val
md/async: don't pass a memory pointer as a page pointer.
md: Fix handling of raid5 array which is being reshaped to fewer devices.
md: fix problems with RAID6 calculations for DDF.
md: remove clumsy usage of do_sync_mapping_range from bitmap code
md: raid1/raid10: handle allocation errors during array setup.
md/raid1/raid10: add a cond_resched
Revert "md: do not progress the resync process if the stripe was blocked"
Vladimir Dronnikov (1):
md: drivers/md/unroll.pl replaced with awk analog
crypto/async_tx/async_pq.c | 40 +++++---
crypto/async_tx/async_raid6_recov.c | 16 ++-
crypto/async_tx/async_xor.c | 18 ++--
drivers/md/Makefile | 22 ++--
drivers/md/bitmap.c | 9 +-
drivers/md/md.c | 2
drivers/md/raid1.c | 6 +
drivers/md/raid10.c | 5 +
drivers/md/raid5.c | 180 ++++++++++++++++++-----------------
drivers/md/raid5.h | 14 ++-
drivers/md/raid6altivec.uc | 2
drivers/md/raid6int.uc | 2
drivers/md/raid6test/Makefile | 42 ++++----
drivers/md/unroll.awk | 20 ++++
drivers/md/unroll.pl | 24 -----
15 files changed, 217 insertions(+), 185 deletions(-)
create mode 100644 drivers/md/unroll.awk
delete mode 100644 drivers/md/unroll.pl
--
Signature
next reply other threads:[~2009-10-16 5:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 5:49 NeilBrown [this message]
2009-10-16 5:49 ` [md PATCH 01/11] Revert "md: do not progress the resync process if the stripe was blocked" NeilBrown
2009-10-16 5:49 ` [md PATCH 06/11] md: drivers/md/unroll.pl replaced with awk analog NeilBrown
2009-10-16 5:49 ` [md PATCH 02/11] md/raid1/raid10: add a cond_resched NeilBrown
2009-10-16 5:49 ` [md PATCH 05/11] md: remove clumsy usage of do_sync_mapping_range from bitmap code NeilBrown
2009-10-16 5:49 ` [md PATCH 04/11] md: raid1/raid10: handle allocation errors during array setup NeilBrown
2009-10-16 5:49 ` [md PATCH 03/11] md/raid5: initialize conf->device_lock earlier NeilBrown
2009-10-16 5:49 ` [md PATCH 10/11] md/async: don't pass a memory pointer as a page pointer NeilBrown
2009-10-16 5:49 ` [md PATCH 07/11] md/raid456: downlevel multicore operations to raid_run_ops NeilBrown
2009-10-16 5:49 ` [md PATCH 09/11] md: Fix handling of raid5 array which is being reshaped to fewer devices NeilBrown
2009-10-16 5:49 ` [md PATCH 11/11] raid6/async_tx: handle holes in block list in async_syndrome_val NeilBrown
2009-10-16 5:49 ` [md PATCH 08/11] md: fix problems with RAID6 calculations for DDF NeilBrown
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=20091016054316.24208.33818.stgit@notabene.brown \
--to=neilb@suse.de \
--cc=dan.j.williams@intel.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).