At a guess.....
The Linux notebook is 10baseT
*IF* the Solaris server is 100baseT (This is the guess) then I would
expect exactly what you are getting.
Using knfsd you will be using UDP. When writting a 5M file Solaris
will start out by sending a few (maybe only 2) 8K UDP packets, which
will fragment into 12 IP datagram. These will arrive at the switch at
100Mb/s and the switch has to slow them down to 10Mb/s. Some will be
lost.
If any fragment of a udp datagram gets lost, the whole datagram is
pretty useless. So effectively no data gets through. In reality it
isn't quite that bad, and the occasionaly 8k udp datagram will get
through, so you do see some thoughput, but not much.
Using nfs-server, you will be using TCP. TCP is much better at
handling lost fragments, and quite possibly solaris will not fragment
at all, but will break up the tcp stream into 1500 (approx) byte ip
packets, and the TCP congention control will work out what is
happening and keep the window to a minium. This was you get much
better throughput.
You should be able to improve throughput with knfsd by setting the
wsize (no need to change rsize) on the mount to < 1500. e.g. 1024.
This way there is no fragmentation, and it should all work better (but
probably not as good as tcp).
Ofcourse, if youyr solaris machine in 10baseX, then I have no idea
what is wrong.
tcp for knfsd is closer with some work that Trond has been doing, but
it'll probably be a 2.5 thing.
NeilBrown
-
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/