Date: Mon, 13 Oct 1997 13:28:47 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Doug Rabson <dfr@nlsystems.com> Cc: Karl Denninger <karl@mcs.net>, Robin Cutshaw <robin@intercore.com>, freebsd-current@freebsd.org Subject: Re: NFS cache problem in 3.0 SNAP Message-ID: <26109.876742127@critter.freebsd.dk> In-Reply-To: Your message of "Mon, 13 Oct 1997 11:09:28 BST." <Pine.BSF.3.95q.971013110610.958A-100000@herring.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> I'm wondering if we need a call from the nfs code to the namecache
>> when the nfs code decides that a directory has been changed. Anybody
>> know where we can detect that situation ?
>
>The nfs client calls nfs_invaldir when it detects a directory chance I
>think.
OK, try to apply this change then:
in kern/vfs_cache.c:
remove static from cache_zap()
Add this function:
void
cache_dir_purge(vp)
struct vnode *vp;
{
while (!LIST_EMPTY(&vp->v_cache_src))
cache_zap(LIST_FIRST(&vp->v_cache_src));
}
in nfs/nfs_subs.c:
And add this call to nfs_invaldir() somewhere:
cache_dir_purge(vp);
And tell me if this improves things...
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?26109.876742127>