> ^^^^^^
> What's the story with the 250Mb/sec sequential block rate? Is the linux
> client caching this data? Should it really be doing this?
With NFSv3 yes. v3 has some very nice ideas. One of these is that write
is a two phase operation. You do a write() you keep the data cached locally
and send it off to the server, later you commit old data and the commit is
allowed to fail forcing a client resend of the write.
The benchmark numbers are probably bogus for real world situations as I suspect
either both or neither would cache normally
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jan 31 2000 - 21:00:12 EST