Whitespace fixes. Bump date for previous.

This commit is contained in:
wiz 2012-08-16 11:28:38 +00:00
parent 6d924f6074
commit 0e61416223
1 changed files with 8 additions and 8 deletions

View File

@ -1,4 +1,4 @@
.\" $NetBSD: puffs_ops.3,v 1.35 2012/08/16 09:25:44 manu Exp $
.\" $NetBSD: puffs_ops.3,v 1.36 2012/08/16 11:28:38 wiz Exp $
.\"
.\" Copyright (c) 2007 Antti Kantee. All rights reserved.
.\"
@ -23,7 +23,7 @@
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.Dd June 27, 2012
.Dd August 16, 2012
.Dt PUFFS_OPS 3
.Os
.Sh NAME
@ -799,18 +799,18 @@ In case the file
has a link count of zero, it may be safely removed now.
.It Fn puffs_node_reclaim2 "pu" "opc" "nlookup"
Same as
.Fn puffs_node_reclaim
.Fn puffs_node_reclaim
with an addditional argument for the number of lookups that have been done
on the node (Node creation is counted as a lookup). This can be used by the
filesystem to avoid a race condition, where the kernel sends a reclaim
while it does not have received the reply for a lookup. If the filesystem
tracks lookup count, and compares to
filesystem to avoid a race condition, where the kernel sends a reclaim
while it does not have received the reply for a lookup.
If the filesystem tracks lookup count, and compares to
.Fa nlookup
it can detect this situation and ignore the reclaim.
it can detect this situation and ignore the reclaim.
.Pp
If the filesystem maps cookies to
.Vt struct puffs_node
then the framework will do that work, and
then the framework will do that work, and
.Fn puffs_node_reclaim
can be reliabily used without the race condition.
.It Fn puffs_node_abortop "pu" "opc" "pcn"