From: Neil Brown <neilb@suse.de>
To: Michael Evans <mjevans1983@gmail.com>
Cc: hank peng <pengxihan@gmail.com>, linux-raid <linux-raid@vger.kernel.org>
Subject: Re: about raid5 recovery when created
Date: Thu, 10 Dec 2009 14:59:31 +1100 [thread overview]
Message-ID: <20091210145931.46ccbfe4@notabene.brown> (raw)
In-Reply-To: <4877c76c0912091934q8ce723ekb83f74bb06c401ba@mail.gmail.com>
On Wed, 9 Dec 2009 19:34:04 -0800
Michael Evans <mjevans1983@gmail.com> wrote:
> On Wed, Dec 9, 2009 at 5:43 PM, Neil Brown <neilb@suse.de> wrote:
> > On Wed, 9 Dec 2009 19:29:04 +0800
> > hank peng <pengxihan@gmail.com> wrote:
> >
> >> I think it is better to implement this function in kernel's md layer.
> >> I wonder what Neil Brown think of this?
> >
> > I don't think it is worth the effort.
> > You probably would save some CPU time as you don't need to XOR, but as has
> > been said, we are usually IO bound, not CPU bound.
> >
> > With the current arrangement, you can start using the array immediately - you
> > don't have to wait for the initial recovery to complete.
> > If you zeroed all devices at create time, you would have to wait for that to
> > complete before using the array.
> >
> > So I see very little gain, and significant cost.
> >
> > NeilBrown
> >
> >
>
> When I assemble an array I tend to have checked the devices before
> hand; it would not be difficult to make the final pass a zeroing pass
> if I knew I could vastly speed up post-assembly performance. As I
> stated, it's merely a lack of clarity in the documentation.
If you would like to create a patch against the man page, I would be happy to
accept it.
NeilBrown
next prev parent reply other threads:[~2009-12-10 3:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 13:01 about raid5 recovery when created hank peng
2009-12-08 13:14 ` Robin Hill
2009-12-08 13:49 ` hank peng
2009-12-08 13:56 ` Robin Hill
2009-12-08 14:03 ` hank peng
2009-12-09 8:30 ` Michael Evans
2009-12-09 11:29 ` hank peng
2009-12-10 1:43 ` Neil Brown
2009-12-10 3:34 ` Michael Evans
2009-12-10 3:59 ` Neil Brown [this message]
[not found] ` <g3143w7eigolu0x2ziUYAxe124vaj_firegpg@mail.gmail.com>
2009-12-30 2:55 ` Neil Brown
[not found] ` <389deec70912090330l73d04696v1d23dbe74423d15b@mail.gmail.com>
2009-12-09 23:29 ` Michael Evans
2009-12-08 13:52 ` hank peng
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=20091210145931.46ccbfe4@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=mjevans1983@gmail.com \
--cc=pengxihan@gmail.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).