From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Fri, 15 Oct 2010 07:54:57 -0700 Message-ID: From: David Leimbach To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=0016e641dde69eab790492a902d1 Subject: Re: [9fans] =?iso-8859-7?q?=F0p?= Topicbox-Message-UUID: 65ca470e-ead6-11e9-9d60-3106f5b1d025 --0016e641dde69eab790492a902d1 Content-Type: text/plain; charset=ISO-8859-1 2010/10/14 Latchesar Ionkov > It can't be dealt with the current protocol. It doesn't guarantee that > Topen will be executed once Twalk is done. So can get Rerrors even if > Twalk succeeds. > > It can be dealt with if the scheduling of the pipeline is done properly. You just have to eliminate the dependencies. I can imagine having a few concurrent queues of "requests" in a client that contain items with dependencies, and running those queues in a pipelined way against a 9P server. > 2010/10/13 Venkatesh Srinivas : > >> 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. > > > > Given careful allocation of FIDs by a client, that can be dealt with - > > operations on an invalid FID just get RErrors. > > > > -- vs > > > > --0016e641dde69eab790492a902d1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

2010/10/14 Latchesar Ionkov <lucho@ionkov.net>
It can't be dealt with the current protocol. It doesn't guarantee t= hat
Topen will be executed once Twalk is done. So can get Rerrors even if
Twalk succeeds.


It can be dealt with if the scheduling= of the pipeline is done properly. =A0You just have to eliminate the depend= encies.

I can imagine having a few concurrent queu= es of "requests" in a client that contain items with dependencies= , and running those queues in a pipelined way against a 9P server.

=A0
2010/10/13 Venkatesh Srinivas <me@acm.= jhu.edu>:
>> 2) you can't pipeline reques= ts 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 i= nvalid.
>
> Given careful allocation of FIDs by a client, that can be dealt with -=
> operations on an invalid FID just get RErrors.
>
> -- vs
>


--0016e641dde69eab790492a902d1--