I don't think so. Because we try to use results from past, and not to look ahead.
On 6/23/07, Roman Shaposhnick <[EMAIL PROTECTED]> 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.
