From owner-freebsd-net Fri Apr 26 10:54:55 2002 Delivered-To: freebsd-net@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 7998737B41A; Fri, 26 Apr 2002 10:54:51 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 51A67AE28D; Fri, 26 Apr 2002 10:54:51 -0700 (PDT) Date: Fri, 26 Apr 2002 10:54:51 -0700 From: Alfred Perlstein To: Brian Candler Cc: freebsd-fs@freebsd.org, freebsd-net@freebsd.org Subject: Re: NFS clearing attribute cache in nfs_open Message-ID: <20020426175451.GG1530@elvis.mu.org> References: <20020426181535.B2748@linnet.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020426181535.B2748@linnet.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * Brian Candler [020426 10:15] wrote: > > Now, there is obviously some "consistency" issue to beware of. Are there any > NFS gurus out there who can say why it is necessary to clear the attribute > cache on _every_ open? Could it safely be made less restrictive, e.g. don't > clear the cache when opening a file for read? I think there are some > potentially large performance gains for diskless server clusters, where the > same file is being repeatedly exec()'d. Open()s should be as consistant as possible, this requires a cache flush. However, If you were to make this a tunable (defaults to off) I would commit it. If you can show that Solaris caches open()s as well I'd be ok with turning it on by default. :) -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message