From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Venti config for booting from fs(3)
Date: Thu, 15 Nov 2007 20:11:42 -0500 [thread overview]
Message-ID: <5a727eb1d46489c965dcb7bfbcfc74eb@quanstro.net> (raw)
In-Reply-To: <38CEF120-B324-41A1-8EB1-781E01CFC57A@gmail.com>
since modern disks can read a whole track at once, there's no "reload"
time. it would only make sense to interleave you have more than 1 i/o
process (venti seems to have a few) and you're either running faster
than the disk bandwidth. the disk bandwidth could be as high as 60MB/s
for sequential reads and as low as 1MB/s for small reads with many seeks.
if most of venti's io is via the read ahead process, i think there would
be very limited benefit by interleaving i/o. and you would need four
disks. if you use two disks partitioned in ½, you will insure that every
write will generate a huge seek.
- erik
next prev parent reply other threads:[~2007-11-16 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 0:38 Anthony Sorace
2007-11-16 1:11 ` erik quanstrom [this message]
2007-11-16 1:10 Joshua Wood
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=5a727eb1d46489c965dcb7bfbcfc74eb@quanstro.net \
--to=quanstro@quanstro.net \
--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).