From: Neil Brown <neilb@suse.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-raid@vger.kernel.org, Ilya Yanok <yanok@emcraft.com>,
Yuri Tikhonov <yur@emcraft.com>
Subject: Re: [PATCH 4/8] md/raid6: asynchronous handle_stripe_fill6
Date: Thu, 4 Jun 2009 16:37:58 +1000 [thread overview]
Message-ID: <18983.27590.350671.321453@notabene.brown> (raw)
In-Reply-To: message from Dan Williams on Wednesday June 3
On Wednesday June 3, dan.j.williams@intel.com wrote:
> From: Yuri Tikhonov <yur@emcraft.com>
>
> Modify handle_stripe_fill6 to work asynchronously by introducing
> fetch_block6 as the raid6 analog of fetch_block5 (schedule compute
> operations for missing/out-of-sync disks).
Following the theme from the previous patch, fetch_block5 is now just
a special case of fetch_block6, so I think it would be best to use the
same code.
Once you do that, handle_stripe_fill6 and handle_stripe_fill5 become
identical, so you only need handle_stripe_fill.
NeilBrown
next prev parent reply other threads:[~2009-06-04 6:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 1:28 [PATCH 0/8] Asynchronous raid6 acceleration (part 3 of 3) Dan Williams
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 [this message]
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=18983.27590.350671.321453@notabene.brown \
--to=neilb@suse.de \
--cc=dan.j.williams@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=yanok@emcraft.com \
--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).