From: Dave Eckhardt <davide+p9@cs.cmu.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: devfs
Date: Tue, 23 Nov 2004 13:31:27 -0500 [thread overview]
Message-ID: <9357.1101234687@piper.nectar.cs.cmu.edu> (raw)
In-Reply-To: <20041123040223.GV44345@cassie.foobarbaz.net>
> 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?
Beware the text beginning with "Since writes go to all
devices in the mirror but reads are performed just by
the first device ..." in the "Setting Up Fossil" Wiki
document,
<http://cm.bell-labs.com/wiki/plan9/setting_up_fossil/index.html>.
Dave Eckhardt
prev parent reply other threads:[~2004-11-23 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 4:02 [9fans] devfs 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
2004-11-23 18:31 ` Dave Eckhardt [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=9357.1101234687@piper.nectar.cs.cmu.edu \
--to=davide+p9@cs.cmu.edu \
--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).