[src/trunk]: src/share/man/man9 Mention that kmem_free(9) may block, just in ...

[rmind <rmind%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/4d5f4e92b5a9
branches:  trunk
changeset: 754204:4d5f4e92b5a9
user:      rmind <rmind%NetBSD.org@localhost>
date:      Fri Apr 23 16:24:04 2010 +0000

description:
Mention that kmem_free(9) may block, just in a case it is not clear.

diffstat:

 share/man/man9/kmem.9 |  12 +++++++++---
 1 files changed, 9 insertions(+), 3 deletions(-)

diffs (41 lines):

diff -r 9a95b8a676b1 -r 4d5f4e92b5a9 share/man/man9/kmem.9
--- a/share/man/man9/kmem.9     Fri Apr 23 16:07:33 2010 +0000
+++ b/share/man/man9/kmem.9     Fri Apr 23 16:24:04 2010 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: kmem.9,v 1.7 2010/02/13 07:44:11 wiz Exp $
+.\"    $NetBSD: kmem.9,v 1.8 2010/04/23 16:24:04 rmind Exp $
 .\"
 .\" Copyright (c)2006 YAMAMOTO Takashi,
 .\" All rights reserved.
@@ -25,7 +25,7 @@
 .\" SUCH DAMAGE.
 .\"
 .\" ------------------------------------------------------------
-.Dd February 11, 2010
+.Dd April 23, 2010
 .Dt KMEM 9
 .Os
 .\" ------------------------------------------------------------
@@ -144,6 +144,9 @@
 allocation.
 This can in turn block other threads that wish to acquire locks held by the
 caller.
+It should be noted that
+.Fn kmem_free
+may also block.
 .Pp
 For some locks this is permissible or even unavoidable.
 For others, particularly locks that may be taken from soft interrupt context,
@@ -263,8 +266,11 @@
 .Xr pool_cache 9
 .\" ------------------------------------------------------------
 .Sh CAVEATS
+Neither
 .Fn kmem_alloc
-cannot be used from interrupt context, from a soft interrupt, or from
+nor
+.Fn kmem_free
+can be used from interrupt context, from a soft interrupt, or from
 a callout.
 Use
 .Xr pool_cache 9