From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <AANLkTikCoXwEp=d6D4uCsU1pOBr=N-rFQARBPj7p_Qb7@mail.gmail.com>
References: <AANLkTimvaNcf3hC8gPAXrFDDs3CKH2ZVa4siS_ihCQvx@mail.gmail.com>
	<AANLkTikCoXwEp=d6D4uCsU1pOBr=N-rFQARBPj7p_Qb7@mail.gmail.com>
Date: Wed, 13 Oct 2010 23:36:21 +0100
Message-ID: <AANLkTimZS1jvvGrtzxZhS=iM4rkje1t=PbYL-rCN1cEO@mail.gmail.com>
From: roger peppe <rogpeppe@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] =?utf-8?b?z4Bw?=
Topicbox-Message-UUID: 63a90ca8-ead6-11e9-9d60-3106f5b1d025

2010/10/13 David Leimbach <leimy2k@gmail.com>:
> I guess I do not understand how 9p doesn't support pipelining. =C2=A0 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 separat=
e
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 i=
t.
if the first operation fails, then subsequent operations will be invalid.

>
> On Wednesday, October 13, 2010, Eric Van Hensbergen <ericvh@gmail.com> wr=
ote:
>> For folks interested in more info on the =CF=80p portion of Noah's Ospre=
y talk,
>> Anant's thesis is available online: http://proness.kix.in/misc/=CF=80p-v=
2.pdf
>>
>> =C2=A0=C2=A0 =C2=A0 =C2=A0-eric
>>
>>
>
>