Messages in this thread | | | Date | Sat, 10 Jan 2004 14:34:12 -0800 | From | Mike Fedyk <> | Subject | Re: 2.6.0 NFS-server low to 0 performance |
| |
On Sat, Jan 10, 2004 at 12:10:46PM +0100, Guennadi Liakhovetski wrote: > On Fri, 9 Jan 2004, Mike Fedyk wrote: > > > On Sat, Jan 10, 2004 at 01:38:00AM +0100, Guennadi Liakhovetski wrote: > > > With 2.6 (on the server, same client) the client reads about 16K at a > > > time, split into 11 fragments, and then packets number 9 and 10 get > > > lost... This all with a StrongARM client and a PCMCIA network-card. With a > > > PXA-client (400MHz compared to 200MHz SA) and an on-board eth smc91x, it > > > gets the first 5 fragments, and then misses every other fragment. Again - > > > in both cases I was copying files to RAM. Yes, 2.6 sends fragments in > > > direct order. > > > > Is that an x86 server, and an arm client? > > Yes. The reason for the problem seems to be the increased default size of > the transfer unit of NFS from 2.4 to 2.6. 8K under 2.4 was still ok, 16K > is too much - only the first 5 fragments pass fine, then data starts to > get lost. If it is a hardware limitation (not all platforms can manage > 16K), it should be probably set back to 8K. If the reason is that some > buffer size was not increased correspondingly, then this should be done. > > Just checked - mounting with rsize=8192,wsize=8192 fixes the problem - > there are again 5 fragments and they all are received properly.
What version is the arm kernel you're running on the client, and where is it from? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |