From: "Fco. J. Ballesteros" <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] devfs
Date: Tue, 23 Nov 2004 15:01:22 +0100 [thread overview]
Message-ID: <35e14588dc09d81d03d2acb6e9cd66b2@plan9.escet.urjc.es> (raw)
In-Reply-To: <a4e6962a041123055326576945@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 291 bytes --]
In our case, we setup mirrors for different partitions in the opposite
order. For example, fossil is sdC0 then sdD0, but venti is sdD0 then
sdC0. This seems to be enough to keep both disks being used at the
same time.
Anyway, nobody here has ever tried to optimize disk usage here.
[-- Attachment #2: Type: message/rfc822, Size: 3616 bytes --]
From: Eric Van Hensbergen <ericvh@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] devfs
Date: Tue, 23 Nov 2004 07:53:36 -0600
Message-ID: <a4e6962a041123055326576945@mail.gmail.com>
On Mon, 22 Nov 2004 21:30:01 -0700, andrey mirtchovski
<mirtchov@cpsc.ucalgary.ca> wrote:
> >>From reading the code, it looks like mirrors in devfs
> > are read preferring the first drive in the mirror, and
> > only reading from the second drive if there's a
> > failure. Is this correct, and if so, is anyone working
> > on round-robin reading to improve read performance?
> >
>
> i believe that is true.
>
> would reading every other block from the second one improve
> performance?
>
What does RAID-1 do? Maybe every other block isn't the right
granularity, but it seems like farming out requests between the
multiple drives would be the right approach.
- eric
next prev parent reply other threads:[~2004-11-23 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 4:02 Christopher Nielsen
2004-11-23 4:30 ` andrey mirtchovski
2004-11-23 13:53 ` Eric Van Hensbergen
2004-11-23 14:01 ` Fco. J. Ballesteros [this message]
2004-11-23 18:31 ` [9fans] devfs Dave Eckhardt
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=35e14588dc09d81d03d2acb6e9cd66b2@plan9.escet.urjc.es \
--to=nemo@lsub.org \
--cc=9fans@cse.psu.edu \
/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).