From: Lars Ellenberg <Lars.Ellenberg@linbit.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Neil Brown <neilb@cse.unsw.edu.au>,
linux-raid@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [patch] latency problem in md driver
Date: Fri, 22 Dec 2006 18:33:35 +0100 [thread overview]
Message-ID: <20061222173335.GB8199@soda.linbit> (raw)
In-Reply-To: <20061222154017.GA8199@soda.linbit>
/ 2006-12-22 16:40:17 +0100
\ Lars Ellenberg:
> the issue at hand is:
> because md does special case the barrier bit, it strips off everything
> else by re-assigning only the io direction and the barrier bit.
>
> ==> I'd like it to also pass at least the sync bit.
some additional info maybe regarding the motivation for this patch.
in drbd 0.7, we have some bitmap on some block device.
this can grow pretty large (128MB), and the code reading/writing it
does synchronous sector size io (which is stupid, and has been changed
already in current drbd svn). --- ok, too much detail ---
anyways, initializing 128MB using 512 Byte bios at a time
with BIO_RW_SYNC using current md raid1 code takes about 5 _minutes_.
with the patch posted earlier, it takes about 5 _seconds_.
this same performance loss will affect every users that are bound
by many small synchronous updates, unless they explicitly unplug
somewhere else.
--
: Lars Ellenberg Tel +43-1-8178292-55 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Vivenotgasse 48, A-1120 Vienna/Europe http://www.linbit.com :
next prev parent reply other threads:[~2006-12-22 17:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-22 14:32 [patch] latency problem in md driver Lars Ellenberg
2006-12-22 15:19 ` Jeff Garzik
2006-12-22 15:37 ` Ric Wheeler
2006-12-22 15:40 ` Lars Ellenberg
2006-12-22 17:33 ` Lars Ellenberg [this message]
2006-12-22 20:40 ` Neil Brown
2006-12-26 13:09 ` Lars Ellenberg
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=20061222173335.GB8199@soda.linbit \
--to=lars.ellenberg@linbit.com \
--cc=akpm@osdl.org \
--cc=jeff@garzik.org \
--cc=linux-raid@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=neilb@cse.unsw.edu.au \
/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).