diff options
author | Thordur I. Bjornsson <thib@cvs.openbsd.org> | 2007-03-23 16:19:39 +0000 |
---|---|---|
committer | Thordur I. Bjornsson <thib@cvs.openbsd.org> | 2007-03-23 16:19:39 +0000 |
commit | 65a46bff133010759fadd89094ccbb6e28ea88f3 (patch) | |
tree | 0d48b3bbd26936c9f0446c4a3425f071201619f4 /share | |
parent | f2b4d392b53b1703e5314a26b4848b8900533d66 (diff) |
remove blather about the v_interlock; Since its now gone.
suggestions and ok jmc@
Diffstat (limited to 'share')
-rw-r--r-- | share/man/man9/vnode.9 | 27 |
1 files changed, 3 insertions, 24 deletions
diff --git a/share/man/man9/vnode.9 b/share/man/man9/vnode.9 index 825fbafb608..a6ead35b167 100644 --- a/share/man/man9/vnode.9 +++ b/share/man/man9/vnode.9 @@ -1,4 +1,4 @@ -.\" $OpenBSD: vnode.9,v 1.24 2007/02/11 13:32:28 bluhm Exp $ +.\" $OpenBSD: vnode.9,v 1.25 2007/03/23 16:19:38 thib Exp $ .\" .\" Copyright (c) 2001 Constantine Sapuntzakis .\" All rights reserved. @@ -90,7 +90,6 @@ struct vnode { struct fifoinfo *vu_fifoinfo; /* fifo (VFIFO) */ } v_un; - struct simplelock v_interlock; /* lock on usecount and flag */ enum vtagtype v_tag; /* type of underlying data */ void *v_data; /* private data for fs */ struct { @@ -187,8 +186,8 @@ method. File systems use this method to free any file-system-specific data they attached to the vnode. .Ss Vnode locks -The vnode actually has three different types of lock: the vnode lock, -the vnode interlock, and the vnode reclamation lock +The vnode actually has two different types of locks: the vnode lock +and the vnode reclamation lock .Pq Dv VXLOCK . .Ss The vnode lock The vnode lock and its consistent use accomplishes the following: @@ -242,26 +241,6 @@ Not all file systems implement it. .Pp To prevent deadlocks, when acquiring locks on multiple vnodes, the lock of parent directory must be acquired before the lock on the child directory. -.Ss Vnode interlock -The vnode interlock -.Pq Va v_interlock -is a simplelock (see -.Xr simple_lock 9 ) . -It is useful on multi-processor systems for acquiring a quick exclusive -lock on the contents of the vnode. -It MUST NOT be held while sleeping. -.Pp -This field protects the -.Va v_flag , v_writecount , v_usecount , -and -.Va v_holdcnt -fields from concurrent access. -See -.Xr lock 9 -for more details on lock synchronization in interrupt context. -.\" Other splbio/interrupt issues? -.Pp -Operations on this lock are a no-op on uniprocessor systems. .Ss Other vnode synchronization The vnode reclamation lock .Pq Dv VXLOCK |