Re: 1000mbps connection problem between Linux and Solaris

I've probably missed some context, but a couple things:

NFS is a request/response protocol. And 32KB isn't enough data at one
time to get link-rate on GbE. So, on reads your NFS client has to be
doing read-ahead, and on writes write-behind to get maybe four or more
requests outstanding onto the wire at one time.

If using UDP, keep in mind that all 22 or so fragments of that 32KB
read/write have to make it through for any of that 32KB read/write to
be good. That means if you have a packet loss probability of p, (1-p)
is the prob of a given fragment getting there, which means that
(1-p)^22 is the probability of all the fragments getting there.

For TCP if one of the segments is lost, it only need retransmit that
segment, not the entire 32KB read/write.

rick jones
--
Process shall set you free from the need for rational thought.
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...
.

Relevant Pages

  • SUMMARY: netstat -p ip output
    ... I can't really up the MTU on this ethernet network, ... I changed the nfs mount rsize and wsize to 1024, ... You can create less fragments ... > two nodes (from Mars to Jupiter). ...
    (Tru64-UNIX-Managers)
  • Re: NFS, how to find out which files are used
    ... NFS doesn't access files by filename, ... by NFS filehandle, ... then matches read/write ops with the filenames that were looked up ...
    (freebsd-questions)