From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <8ccc8ba40706221727t51aeeb57x1d7d0d86cbe5ea51@mail.gmail.com>
Date: Sat, 23 Jun 2007 02:27:04 +0200
From: "Francisco J Ballesteros" <nemo@lsub.org>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] About 9P ...
In-Reply-To: <1182558450.25089.429.camel@work.sfbay.sun.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <3e1162e60706221446n2645b7f4ncd00b2bb177b837c@mail.gmail.com>
	<53d7cfa0a8bb5d6ce90bffdccc278ee0@9netics.com>
	<8ccc8ba40706221648i3d1ef70m6272c383d9f12983@mail.gmail.com>
	<1182558450.25089.429.camel@work.sfbay.sun.com>
Topicbox-Message-UUID: 85dfaef2-ead2-11e9-9d60-3106f5b1d025

I don't think so. Because we try to use results from past, and not to
look ahead.


On 6/23/07, Roman Shaposhnick <rvs@sun.com> wrote:
> On Sat, 2007-06-23 at 01:48 +0200, Francisco J Ballesteros wrote:
> > Skip wrote:
> > :there were discussions about aysnc syscalls.  /sys/src/cmd/fcp.c is a
> > :good example of why they're not needed.  streaming and long delay
> > :networks can be handled this way too, as was pointed out (by Russ i
> > :think) at iwp9.
> >
> > But there is one problem. Consider "lc".
> >
> > Usually you see
> > walk
> > clunk
> > walk
> > clunk
> > walk
> > open
> > write
> > clunk
> >
> > and also
> > walk
> > stat clunk
> > walk
> > open
> > read
> > clunk
> >
> > The problem is, how to know which RPCs to pack?
>
>   Isn't it the very same problem that compilers have with
> instruction pipelining?
>    http://en.wikipedia.org/wiki/Instruction_pipelining
>
>   With an additional complication that you can't actually
> look ahead very often?
>
> Thanks,
> Roman.
>
>