From: Neil Brown <neilb@suse.de>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Stripe dirty bitmap
Date: Mon, 5 Jul 2010 11:02:03 +1000 [thread overview]
Message-ID: <20100705110203.01502ac1@notabene.brown> (raw)
In-Reply-To: <4C3126C0.4050709@tmr.com>
On Sun, 04 Jul 2010 20:26:40 -0400
Bill Davidsen <davidsen@tmr.com> wrote:
> Sure would be nice to have md track whole never written stripes, so
> creating an array didn't have to be done over a three day weekend. When
> any part of a virgin stripe was written it could then be initialized
> properly, and when a virgin stripe was read zeros could be returned
> without disk i/o. It doesn't matter that the reads are done in parallel,
> with modern disk the bus is the bottleneck. With eSATA arrays the bus is
> slow to start with, passing TB through it should be avoided if possible.
>
Sure would.
NeilBrown
next prev parent reply other threads:[~2010-07-05 1:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 0:26 Stripe dirty bitmap Bill Davidsen
2010-07-05 1:02 ` Neil Brown [this message]
2010-07-05 1:24 ` Bill Davidsen
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=20100705110203.01502ac1@notabene.brown \
--to=neilb@suse.de \
--cc=davidsen@tmr.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