From: roger peppe <rogpeppe@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] πp
Date: Wed, 13 Oct 2010 23:36:21 +0100 [thread overview]
Message-ID: <AANLkTimZS1jvvGrtzxZhS=iM4rkje1t=PbYL-rCN1cEO@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikCoXwEp=d6D4uCsU1pOBr=N-rFQARBPj7p_Qb7@mail.gmail.com>
2010/10/13 David Leimbach <leimy2k@gmail.com>:
> I guess I do not understand how 9p doesn't support pipelining. All
> requests are tagged and can be dealt with between client and server in
> any order right?
two issues (at least):
1) concurrently sent requests can be reordered (they're serviced in separate
threads on the server) which means that, when reading from a streaming file
which ignores file offsets, you don't necessarily get data back in the
order that
you asked for it.
2) you can't pipeline requests if the result of one request depends on the
result of a previous. for instance: walk to file, open it, read it, close it.
if the first operation fails, then subsequent operations will be invalid.
>
> On Wednesday, October 13, 2010, Eric Van Hensbergen <ericvh@gmail.com> wrote:
>> For folks interested in more info on the πp portion of Noah's Osprey talk,
>> Anant's thesis is available online: http://proness.kix.in/misc/πp-v2.pdf
>>
>> -eric
>>
>>
>
>
next prev parent reply other threads:[~2010-10-13 22:36 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 19:46 Eric Van Hensbergen
2010-10-13 22:13 ` David Leimbach
2010-10-13 22:36 ` roger peppe [this message]
2010-10-13 23:15 ` David Leimbach
2010-10-14 4:25 ` blstuart
2010-10-13 23:24 ` Venkatesh Srinivas
2010-10-14 21:12 ` Latchesar Ionkov
2010-10-14 21:48 ` erik quanstrom
2010-10-14 22:14 ` dorin bumbu
2010-10-15 14:07 ` erik quanstrom
2010-10-15 14:45 ` Russ Cox
2010-10-15 15:41 ` Latchesar Ionkov
2010-10-15 21:13 ` dorin bumbu
2010-10-15 22:13 ` erik quanstrom
2010-10-15 23:30 ` dorin bumbu
2010-10-15 23:45 ` cinap_lenrek
2010-10-15 23:54 ` dorin bumbu
2010-10-15 7:24 ` Sape Mullender
2010-10-15 10:41 ` hiro
2010-10-15 12:11 ` Jacob Todd
2010-10-15 13:06 ` Iruatã Souza
2010-10-15 13:23 ` Sape Mullender
2010-10-15 14:57 ` David Leimbach
2010-10-15 14:54 ` David Leimbach
2010-10-15 14:59 ` Francisco J Ballesteros
2010-10-15 16:19 ` cinap_lenrek
2010-10-15 16:28 ` Lyndon Nerenberg
2010-10-15 17:54 ` Nemo
2010-10-15 17:49 ` ron minnich
2010-10-15 18:56 ` erik quanstrom
2010-10-15 16:31 ` Latchesar Ionkov
2010-10-15 16:40 ` cinap_lenrek
2010-10-15 16:43 ` Latchesar Ionkov
2010-10-15 17:11 ` cinap_lenrek
2010-10-15 17:15 ` Latchesar Ionkov
2010-10-15 19:10 ` erik quanstrom
2010-10-15 19:16 ` Latchesar Ionkov
2010-10-15 21:43 ` Julius Schmidt
2010-10-15 22:02 ` David Leimbach
2010-10-15 22:05 ` John Floren
2010-10-15 16:45 ` ron minnich
2010-10-15 17:26 ` Eric Van Hensbergen
2010-10-15 17:45 ` Charles Forsyth
2010-10-15 17:45 ` ron minnich
2010-10-15 18:03 ` Bakul Shah
2010-10-15 18:45 ` David Leimbach
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='AANLkTimZS1jvvGrtzxZhS=iM4rkje1t=PbYL-rCN1cEO@mail.gmail.com' \
--to=rogpeppe@gmail.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).