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: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: raid io requests not parallel?
Date: Sat, 15 Jul 2006 23:17:35 -0400	[thread overview]
Message-ID: <200607152320_MC3-1-C51B-11C9@compuserve.com> (raw)

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

On Sat, 15 Jul 2006 17:04:57 -0700, Jonathan Baccash wrote:

> As expected, the multi-threaded reads are 2x as fast as single-threaded
> reads. But I would have expected (assuming the write to both disks can
> occur in parallel) that the random writes are about the same speed (10
> seconds) as the single-threaded random reads, for both the
> single-threaded and multi-threaded write cases. The fact that the
> multi-threaded reads were
> twice as fast indicates to me that read requests can occur in parallel.
> 
> So.... why doesn't the raid issue the writes in parallel? Thanks in
> advance for any help.

But it does issue writes in parallel.  The problem is in the way RAID1
works.  When you do a read from the RAID1, it issues one read request
to one of the underlying disks.  When you do a write, it issues one write
request to _each_ of the underlying disks.  So with two disks in the
mirror set, every write issued by your program causes two disk writes.

-- 
Chuck
 "You can't read a newspaper if you can't read."  --George W. Bush

             reply	other threads:[~2006-07-16  3:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-16  3:17 Chuck Ebbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-16 20:08 Chuck Ebbert
2006-07-16 22:57 ` Jonathan Baccash
     [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=200607152320_MC3-1-C51B-11C9@compuserve.com \
    --to=76306.1226@compuserve.com \
    --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

all inboxes | Powered by JetHome®