vget(9) [minix man page]

VGET(9) 						   BSD Kernel Developer's Manual						   VGET(9)

NAME

     vget -- get a vnode from the free list

SYNOPSIS

     #include <sys/param.h>
     #include <sys/vnode.h>

     int
     vget(struct vnode *vp, int lockflag, struct thread *td);

DESCRIPTION

     Get a vnode from the free list and increment its reference count.

     vp        The vnode to remove from the free list.

     lockflag  If non-zero, the vnode will also be locked.

     When not in use, vnodes are kept on a free list.  The vnodes still reference valid files but may be reused to refer to a new file at any
     time.  Often, these vnodes are also held in caches in the system, such as the name cache.

     When a vnode which is on the free list is used again, for instance if the vnode was found in the name cache as a result of a call to
     VOP_LOOKUP(9) then the new user must call vget() to increment the reference count and remove it from the free list.

SEE ALSO

     vnode(9), vput(9), vref(9), vrele(9)

AUTHORS

     This manual page was written by Doug Rabson.

BSD
								   July 24, 1996							       BSD

VRELE(9)						   BSD Kernel Developer's Manual						  VRELE(9)

NAME

     vput, vrele, vunref -- decrement the use count for a vnode

SYNOPSIS

     #include <sys/param.h>
     #include <sys/vnode.h>

     void
     vput(struct vnode *vp);

     void
     vrele(struct vnode *vp);

     void
     vunref(struct vnode *vp);

DESCRIPTION

     Decrement the v_usecount field of a vnode.

     vp  the vnode to decrement

     The vrele() function takes an unlocked vnode and returns with the vnode unlocked.

     The vput() function should be given a locked vnode as argument, the vnode is unlocked after the function returned.  The vput() is opera-
     tionally equivalent to calling VOP_UNLOCK(9) followed by vrele(9), with less overhead.

     The vunref() function takes a locked vnode as argument, and returns with the vnode locked.

     Any code in the system which signified its use of a vnode by usecount should call one of the listed function to decrement use counter.  If
     the v_usecount field of the non-doomed vnode reaches zero, then it will be inactivated and placed on the free list.  Since the functions
     might need to call VOPs for the vnode, the Giant mutex should be conditionally locked around the call.

     The hold count for the vnode is always greater or equal to the usecount.  Non-forced unmount fails when mount point owns a vnode that has
     non-zero usecount, see vflush(9).

SEE ALSO

     vget(9), vnode(9), vref(9), vrefcnt(9)

AUTHORS

     This manual page was written by Doug Rabson and
     Konstantin Belousov.

BSD
								 November 20, 2010							       BSD