Source-Changes-HG archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

[src/trunk]: src/share/man/man9 Refer to locks by their correct names as desc...



details:   https://anonhg.NetBSD.org/src/rev/70f648651a82
branches:  trunk
changeset: 511968:70f648651a82
user:      gmcgarry <gmcgarry%NetBSD.org@localhost>
date:      Sun Jul 01 03:13:20 2001 +0000

description:
Refer to locks by their correct names as described lock(9).

diffstat:

 share/man/man9/extent.9 |  8 ++++++--
 1 files changed, 6 insertions(+), 2 deletions(-)

diffs (22 lines):

diff -r b3a17ed2fe42 -r 70f648651a82 share/man/man9/extent.9
--- a/share/man/man9/extent.9   Sun Jul 01 02:58:38 2001 +0000
+++ b/share/man/man9/extent.9   Sun Jul 01 03:13:20 2001 +0000
@@ -1,4 +1,4 @@
-.\" $NetBSD: extent.9,v 1.17 2001/06/21 11:59:00 wiz Exp $
+.\" $NetBSD: extent.9,v 1.18 2001/07/01 03:13:20 gmcgarry Exp $
 .\"
 .\" Copyright (c) 1996, 1998 The NetBSD Foundation, Inc.
 .\" All rights reserved.
@@ -280,7 +280,11 @@
 .Sh LOCKING
 The extent manager performs all necessary locking on the extent map
 itself, and any other data structures internal to the extent manager.
-The locks used by the extent manager are spin locks, and will never sleep.
+The locks used by the extent manager are simplelocks, and will never sleep
+.Po
+see 
+.Xr lock 9
+.Pc .
 This should be taken into account when designing the locking protocol
 for users of the extent manager.
 .Sh RETURN VALUES



Home | Main Index | Thread Index | Old Index