From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9p vs http
Date: Tue, 16 Nov 2010 07:42:13 -0500 [thread overview]
Message-ID: <AANLkTi=mJYkUqR1L=nuCToQLOFeCj=m=wiwUkrzi_XgC@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikkxwva0SM+V+GQeFnpTw2Rn568+5YSwfziBwn2@mail.gmail.com>
On Mon, Nov 15, 2010 at 2:00 PM, Dan Adkins <dadkins@gmail.com> wrote:
> That brings up a question of interest to me. How do you effectively
> read ahead with the 9p protocol? Even if you issued many read
> requests in parallel, the server is allowed to return less data than
> was asked for. You'll end up with holes in your buffer that require
> at least another roundtrip to fill.
The traditional "store data" file servers that Unix users
would recognize tend to follow the Unix semantics that
a read will return as much data as it can. If you're talking
to one of them you issue reads for 8k each or whatever
and then do the roundtrip if necessary, but it rarely is.
Russ
prev parent reply other threads:[~2010-11-16 12:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 3:25 Sam Watkins
2010-11-15 4:20 ` John Floren
2010-11-15 4:26 ` Bruce Ellis
2010-11-15 5:16 ` Sam Watkins
2010-11-15 5:26 ` John Floren
2010-11-15 14:09 ` Gorka Guardiola
2010-11-15 14:15 ` Gorka Guardiola
2010-11-15 15:37 ` roger peppe
2010-11-15 16:45 ` C H Forsyth
2010-11-15 16:37 ` roger peppe
2010-11-15 16:48 ` erik quanstrom
2010-11-15 17:02 ` roger peppe
2010-11-15 19:29 ` erik quanstrom
2010-11-15 21:38 ` roger peppe
2010-11-16 1:18 ` erik quanstrom
2010-11-16 12:12 ` roger peppe
2010-11-16 15:56 ` Charles Forsyth
2010-11-16 16:04 ` erik quanstrom
2010-11-16 16:32 ` Charles Forsyth
2010-11-16 17:11 ` roger peppe
2010-11-15 15:44 ` David Leimbach
2010-11-15 15:55 ` Venkatesh Srinivas
2010-11-15 15:57 ` David Leimbach
2010-11-15 18:44 ` Russ Cox
2010-11-15 19:00 ` Dan Adkins
2010-11-15 22:18 ` Yaroslav
2010-11-15 22:34 ` erik quanstrom
2010-11-16 12:42 ` Russ Cox [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='AANLkTi=mJYkUqR1L=nuCToQLOFeCj=m=wiwUkrzi_XgC@mail.gmail.com' \
--to=rsc@swtch.com \
--cc=9fans@9fans.net \
/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).