From: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: linus 2.4.20 nfs performance problem
Date: Tue, 16 Mar 2004 11:08:28 -0500
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <1079453308.3045.26.camel@lade.trondhjem.org>
References: <8147E1B07201DD41B6B9F0D31E07B38401648904@srv-grp-s07.dev.atos.fr>
	 <039c01c40b5b$cc2f06e0$3f32a8c0@ds.ig.com.br>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Cc: nfs@lists.sourceforge.net
To: Fabiano Reis <silos.reis@ig.com.br>
In-Reply-To: <039c01c40b5b$cc2f06e0$3f32a8c0@ds.ig.com.br>
Errors-To: nfs-admin@lists.sourceforge.net

P=E5 ty , 16/03/2004 klokka 08:37, skreiv Fabiano Reis:
> looks like you are getting the maximum number of nfs operations by
> mountpoint. See nfs.sourceforge.net
>=20
> The maximum nfs operations by mountpoint for kernel < 2.5.47 is 256
>=20
> I=B4m getting the same problem with kernel 2.4.20. I ipgraded a nfs clien=
t to
> kernel 2.6 and I still getting the same problem. Maybe a solution is to
> upgrade the server and client to kernel 2.6 (I didnt tested it yet)

There is a second limit: the RPC client limits the number of RPC
requests it can have outstanding on the wire.

On TCP, that limit is always 16 requests. On UDP, there is a congestion
control algorithm that will reduce that limit dynamically if the network
is losing packets (or if the server is dropping them).

Note: 2.6.5-rc1 contains a patch by Chuck Lever that allows you to
change that upper limit of 16 requests by means of a /proc interface.

Cheers,
 Trond


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs