Subject: Re: vnode locking procedure change to suport stacked fs's.
To: Jason Thorpe <email@example.com>
From: Bill Sommerfeld <firstname.lastname@example.org>
Date: 06/01/1999 20:25:48
> > My thought was to just have getnewvnode() ignore the previous contents of
> > v_vnlock (the pointer) and initialize it to &vp->v_lock (the struct
> > lock).
> ...along these lines... is it possible for vnodes which are still
> referenced to actually be on the free list?
If I recall correctly, the name lookup cache contains pointers to them
but doesn't hold a reference.
A generation number scheme is used to notice when vnodes get reused.
> If not, then I'd like to nuke the free list completely, and
> pool_put() vnodes when they're no longer used (so that free vnode
> pool pages can be reclaimed if necessary).
Hmm. I would think that this would reduce efficiency somewhat, as
vnodes couldn't be reclaimed from the freelist..