I am having problems with timeouts and generaly throughput in
the 2.4.3 NFS client side code which are not present in the
2.4.2 kernel running in the same configuraiton on the same
hardware. The machines are on a 100 Mbit switched local
network with essentially no other trafic.
In both cases, testing against a 2.4.3 NFS server (using
knfsd). My tests involved using "dd" to read a large file on
an NFS mounted directory and running the "connectathon" NFS
test suite.
When I boot my client machine with 2.4.3, reading a 327 Mbyte
file over NFS takes on the order of 5-6 minutes to complete.
If I run the same command witrh the client running kernel
2.4.2, the command completes in about 1 minute.
Running the "cthon01" test suite, the 2.4.3 client machine
basically hangs in the "read + write" test section and I
didn't bother waiting for it to finish. Again, when switching
back to 2.4.2, the client runs through the tests quite
quickly.
From my tests I'm pretty convinced that something in either
the NFS client code or the networking layer has changed which
has drastically reduced NFS client speeds in 2.4.3.
Is this a known problem? Can I provide any additional
information to help debug it?
--
cae at bklyn dot org | Caleb Epstein | bklyn . org | Brooklyn Dust Bunny Mfg.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
