vop_inactive(9) [debian man page]

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

NAME

     VOP_INACTIVE, VOP_RECLAIM -- reclaim file system resources for a vnode

SYNOPSIS

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

     int
     VOP_INACTIVE(struct vnode *vp, struct thread *td);

     int
     VOP_RECLAIM(struct vnode *vp, struct thread *td);

DESCRIPTION

     The arguments are:

     vp  The vnode being reclaimed.

     VOP_INACTIVE() is called when the kernel is no longer using the vnode.  This may be because the reference count reaches zero or it may be
     that the file system is being forcibly unmounted while there are open files.  It can be used to reclaim space for 'open but deleted' files.

     VOP_RECLAIM() is called when a vnode is being reused for a different file system.	Any file system specific resources associated with the
     vnode should be freed.

LOCKS

     For VOP_INACTIVE, the vp will be locked on entry.	Your VOP_INACTIVE code must unlock the vp prior to returning.

     For VOP_RECLAIM, the vp will not be locked on entry and should be left unlocked on return.

SEE ALSO

     vnode(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