linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alex" <alexcos@nights.ro>
To: linux-raid@vger.kernel.org
Subject: Fw: Raid1 questions (devel)
Date: Thu, 16 Sep 2004 00:20:56 +0300	[thread overview]
Message-ID: <001601c49b69$e4e809e0$6400a8c0@alex> (raw)

> > Hello..
> >
> > I'm not sure if you are still developing the raid1 module for linux
kernel , but I'll give a shot.
> >
> > Checking the source code of linux.2.6.8.1 , in raid1.c , at line 411 I
found this:
> >     "Don't change to another disk for sequential reads"
> >
> > Well , my question is this:
> >
> >     If there is a sequential read , but there are other disks in the
array which are idle , isn't it a better way to read in chunks from all the
disks ?  I think the transfer rate will be much improved from reading from
more disks , rather the using only one  (altough is sequential read)
> >
> >
> > Thanks
> >     Alex
>


             reply	other threads:[~2004-09-15 21:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-15 21:20 Alex [this message]
2004-09-15 22:49 ` Fw: Raid1 questions (devel) Neil Brown

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='001601c49b69$e4e809e0$6400a8c0@alex' \
    --to=alexcos@nights.ro \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).