From: splite@purdue.edu
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: 9p & read-ahead
Date: Thu, 31 Jul 2003 10:07:31 -0500 [thread overview]
Message-ID: <20030731100731.A12927@sigint.cs.purdue.edu> (raw)
In-Reply-To: <Pine.LNX.4.33.0307310626500.15683-100000@einstein.ssz.com>; from ravage@einstein.ssz.com on Thu, Jul 31, 2003 at 06:27:24AM -0500
On Thu, Jul 31, 2003 at 06:27:24AM -0500, Jim Choate wrote:
>
> On Thu, 31 Jul 2003 steve.simon@snellwilcox.com wrote:
>
> > Anyone any strong views about this?
>
> Add a switch so that anyone who does in a negative way can turn it off.
And a light to indicate that it's on.
And a rheostat to control how much it reads ahead.
next prev parent reply other threads:[~2003-07-31 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 8:29 [9fans] " steve.simon
2003-07-31 8:37 ` boyd, rounin
2003-07-31 9:44 ` Bruce Ellis
2003-07-31 9:50 ` boyd, rounin
2003-07-31 20:52 ` rog
2003-07-31 11:27 ` [9fans] " Jim Choate
2003-07-31 15:07 ` splite [this message]
2003-07-31 16:04 ` Jack Johnson
2003-07-31 23:36 ` [9fans] " Geoff Collyer
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=20030731100731.A12927@sigint.cs.purdue.edu \
--to=splite@purdue.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).