Subject: Re: vnode locking procedure change to suport stacked fs's.
To: Jason Thorpe <>
From: Bill Studenmund <>
List: tech-kern
Date: 06/01/1999 11:55:05
On Tue, 1 Jun 1999, Jason Thorpe wrote:

> On Tue, 1 Jun 1999 11:38:36 -0700 (PDT) 
>  Bill Studenmund <> wrote:
>  > 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 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).

Actualy, still-referenced vnodes are not supposed to get on the free list.
All the code paths which insert onto the free list only do so if the
usecount is <=0 (with the < part causing panics ifdef DIAGNOSTIC in a few

So you could pool_put them.

Take care,