public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Goswin von Brederlow <goswin-v-b@web.de>
To: Michael Evans <mjevans1983@gmail.com>
Cc: Matthieu Patou <mat@matws.net>,
	Goswin von Brederlow <goswin-v-b@web.de>,
	Asdo <asdo@shiftmail.org>,
	linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Random IO with md raid
Date: Wed, 16 Dec 2009 12:32:20 +0100	[thread overview]
Message-ID: <87zl5j6tob.fsf@frosties.localdomain> (raw)
In-Reply-To: <4877c76c0912140213u3dab2fcfxfd7ed1b4ff79f4ad@mail.gmail.com> (Michael Evans's message of "Mon, 14 Dec 2009 02:13:39 -0800")

Michael Evans <mjevans1983@gmail.com> writes:

> On Mon, Dec 14, 2009 at 1:06 AM, Matthieu Patou <mat@matws.net> wrote:
>> Hello Goswin,
>>> Software raid1 will write twice as much data. That means twice as much
>>> data goes over the system bus and into the controler cache.
>>> Effectively you have halve the cache size. Maybe that is all you see.
>>>
>>> MfG
>>>          Goswin
>>>
>> Your idea seems logical, and I took a few hours today to verify it and it's
>> the case as accessing the disk without software raid leads to almost the
>> same result as with hardware raid.
>>
>> Matthieu.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>
> Thinking about it, the doubling of data going over the system bus part
> is correct.  You must still push the operation out to each device's
> buffer.  However for -most- modern systems the system-bus will not be
> the bottleneck for a reasonable number of drives.
>
> Further the later half which I'd skimmed over the first time is
> utterly incorrect.  Each drive would still only see the commands
> targeting that drive.  That should be virtually the same if not
> identical to the single-drive case.

The controler itself has cache. And that is shared between all drives.

> The two most likely bottlenecks are single-drive write speed, and any
> IO barriers that are used to ensure file system consistency in the
> event of sudden interruption.

MfG
        Goswin
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-12-16 11:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-04 22:31 Random IO with md raid Matthieu Patou
2009-12-05 14:20 ` Asdo
2009-12-07 22:59   ` Matthieu Patou
2009-12-09 16:36     ` Goswin von Brederlow
2009-12-14  9:06       ` Matthieu Patou
2009-12-14 10:13         ` Michael Evans
2009-12-16 11:32           ` Goswin von Brederlow [this message]

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=87zl5j6tob.fsf@frosties.localdomain \
    --to=goswin-v-b@web.de \
    --cc=asdo@shiftmail.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=mat@matws.net \
    --cc=mjevans1983@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