From: "Jose R. Santos" Subject: dentry/inode cache invalidation when using nfsd filesystem on 2.6 Date: Tue, 21 Oct 2003 09:24:14 -0500 Sender: nfs-admin@lists.sourceforge.net Message-ID: <20031021142414.GW1516@dbz.austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; Format=Flowed; DelSp=Yes; charset=ISO-8859-1 Cc: Linux NFS Mailing List Return-path: Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.11] helo=sc8-sf-mx1.sourceforge.net) by sc8-sf-list1.sourceforge.net with esmtp (Cipher TLSv1:DES-CBC3-SHA:168) (Exim 3.31-VA-mm2 #1 (Debian)) id 1ABxR4-00059N-00 for ; Tue, 21 Oct 2003 07:24:34 -0700 Received: from e35.co.us.ibm.com ([32.97.110.133]) by sc8-sf-mx1.sourceforge.net with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.22) id 1ABxR3-00087i-Sx for nfs@lists.sourceforge.net; Tue, 21 Oct 2003 07:24:33 -0700 To: Neil Brown Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: Hi, I have come across a interesting behavior when using NFS server on machines with large amounts of memory(16/32Gb). If I have exported filesystems with lots of data and many directories that were access and had dentry/inode cache entries cached on the server, the clients took a long time(sometimes minutes) to mount the NFS exported directories. While the client was mostly IDLE, the servers rpc.mountd thread was consuming 100% of one CPU on the system. After some digging, I found that the problem lies on the new nfsd filesystem code that talks to nfsctl. Every time I issue a mount on the client, the server invalidates both inode and dentry caches. Inode cache get invalidated on sys_nfsservctl(fs/nfsctl.c) on the fput call which eventually calls invalidate_inodes. Dentry caches get invalidated on do_open(fs/nfsctl.c) when calling do_kernel_mount which eventually calls shrink_dcache_sb. The inode cache invalidation is easy to work around by just mounting the nfsd to something like /tmp/nfsd, but I haven't been able(except with a very dangerous and stupid patch) to work around the dentry cache invalidation. This invalidation seem unnecessary and it cause by the interaction with this new interface for nfsctl. Any help would be appreciated. :) Thanks - JRS ------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs