From: "Bruce Ellis" <brucee@chunder.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] 9p & read-ahead
Date: Thu, 31 Jul 2003 19:44:28 +1000 [thread overview]
Message-ID: <004b01c35748$b8796090$c901a8c0@cc77109e> (raw)
In-Reply-To: <28cbe19e5474cf6db7ca08daae97e949@yourdomain.dom>
read-ahead is straightforward and has been done a few times under
different moons. the server decides the policy and if gets it wrong
then you know who to blame. write-ahead is more interesting and
has been done a few times (by pb and me at least) - write-ahead
being an immediate Rwrite when you are the policy man. (write errors
poison the chan so the next T* gets an Rerror.) great for annoying
people by streaming video in the unix room.
brucee
----- Original Message -----
From: <steve.simon@snellwilcox.com>
To: <9fans@cse.psu.edu>
Sent: Thursday, July 31, 2003 6:29 PM
Subject: [9fans] 9p & read-ahead
> Hi,
>
> I am thinking of adding read-ahead to a 9p server.
> Is this a sensible thing to do? Am I being foolish
> and indulging in bloatware or is it a sensible
> optimisation?
etc
next prev parent reply other threads:[~2003-07-31 9:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 8:29 steve.simon
2003-07-31 8:37 ` boyd, rounin
2003-07-31 9:44 ` Bruce Ellis [this message]
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
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='004b01c35748$b8796090$c901a8c0@cc77109e' \
--to=brucee@chunder.com \
--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).