mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: "Jonathan Baccash" <jbaccash@gmail.com>
Cc: Ava Kivity <avi@argo.co.il>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: raid io requests not parallel?
Date: Sun, 16 Jul 2006 16:08:25 -0400	[thread overview]
Message-ID: <200607161609_MC3-1-C52A-F449@compuserve.com> (raw)

In-Reply-To: <e0e4cb3e0607160938k70819e40g4172f5917045ebf8@mail.gmail.com>

On Sun, 16 Jul 2006 09:38:25 -0700, Jonathan Baccash wrote:

> > Each head has to service 1024 write requests (compared to just 512 read
> > requests).
>
> By that logic, it would take twice as long for my writes to finish.
> Why is it taking 4x as long in my parallel test?

Because a single read not only goes to just one disk, it is sent to
the disk with the lowest expected seek time for that request.  This
cuts average read time in half, on average.

(See drivers/md/raid1.c::read_balance().)

> I would expect a raid-1 write
> to take about as long to write a single block as a single write to a
> single disk (assuming no other disk activity), because I would expect
> two writes to happen concurrently.

You didn't post any benchmarks showing results for single write to a
single disk.

-- 
Chuck
 Think. Or you will be replaced with a small shell script.  --dwmw2

             reply	other threads:[~2006-07-16 20:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-16 20:08 Chuck Ebbert [this message]
2006-07-16 22:57 ` Jonathan Baccash
  -- strict thread matches above, loose matches on Subject: below --
2006-07-16  3:17 Chuck Ebbert
     [not found] <fa.di4ao4hbHlmvf0KHMl+KieWzn2E@ifi.uio.no>
2006-07-16  1:41 ` Robert Hancock
2006-07-16  0:04 Jonathan Baccash
2006-07-16  1:07 ` Arjan van de Ven
2006-07-16  5:46 ` Avi Kivity
2006-07-16 16:38   ` Jonathan Baccash
2006-07-16 23:59 ` Neil Brown
2006-07-17  0:20   ` Jens Axboe

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=200607161609_MC3-1-C52A-F449@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=avi@argo.co.il \
    --cc=jbaccash@gmail.com \
    --cc=linux-kernel@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

Powered by JetHome