From: Russell Coker <russell@coker.com.au>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org, pkg-mdadm-devel@lists.alioth.debian.org
Subject: Re: write-intent bitmaps
Date: Mon, 28 Jan 2008 02:12:20 +1100 [thread overview]
Message-ID: <200801280212.25381.russell@coker.com.au> (raw)
In-Reply-To: <18332.26941.370395.885100@notabene.brown>
On Sunday 27 January 2008 22:21, Neil Brown <neilb@suse.de> wrote:
> On Sunday January 27, russell@coker.com.au wrote:
> > http://lists.debian.org/debian-devel/2008/01/msg00921.html
> >
> > Are they regarded as a stable feature? If so I'd like to see
> > distributions supporting them by default. I've started a discussion in
> > Debian on this topic, see the above URL for details.
>
> Yes, it is regarded as stable.
Thanks for that information.
> However it can be expected to reduce write throughput. A reduction of
> several percent would not be surprising, and depending in workload it
> could probably be much higher.
It seems to me that losing a few percent of performance all the time is better
than a dramatic performance loss for an hour or two when things go wrong.
> It is quite easy to add or remove a bitmap on an active array, so
> making it a default would probably be fine providing it was easy for
> an admin to find out about it and remove the bitmap is they wanted the
> extra performance.
I hadn't realised that. So having this in the installer is not as important
as I previously thought.
--
russell@coker.com.au
http://etbe.coker.com.au/ My Blog
http://www.coker.com.au/sponsorship.html Sponsoring Free Software development
next prev parent reply other threads:[~2008-01-27 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 10:34 write-intent bitmaps Russell Coker
2008-01-27 11:21 ` Neil Brown
2008-01-27 15:12 ` Russell Coker [this message]
[not found] ` <479E1BB3.2080702@tmr.com>
2008-01-29 7:32 ` Russell Coker
2008-01-29 9:13 ` Peter Rabbitson
2008-01-29 9:40 ` Russell Coker
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=200801280212.25381.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=pkg-mdadm-devel@lists.alioth.debian.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).