Attachment 95643 Details for Bug 134074 – file.diff

[patch] file.diff

file.diff (text/plain), 2.74 KB, created by Haven Hash on 2009-04-29 01:20:03 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Haven Hash

Created: 2009-04-29 01:20:03 UTC

Size: 2.74 KB

patch

obsolete

>Index: share/man/man9/locking.9
>===================================================================
>--- share/man/man9/locking.9	(revision 191639)
>+++ share/man/man9/locking.9	(working copy)
>@@ -220,28 +220,6 @@
> When a thread waits on a condition, the mutex
> is atomically released before the thread is blocked, then reacquired
> before the function call returns.
>-.Ss Giant
>-Giant is a special instance of a sleep lock.
>-It has several special characteristics.
>-.Bl -enum
>-.It
>-It is recursive.
>-.It
>-Drivers can request that Giant be locked around them, but this is
>-going away.
>-.It
>-You can sleep while it has recursed, but other recursive locks cannot.
>-.It
>-Giant must be locked first before other locks.
>-.It
>-There are places in the kernel that drop Giant and pick it back up
>-again.
>-Sleep locks will do this before sleeping.
>-Parts of the Network or VM code may do this as well, depending on the
>-setting of a sysctl.
>-This means that you cannot count on Giant keeping other code from
>-running if your code sleeps, even if you want it to.
>-.El
> .Ss Sleep/wakeup
> The functions
> .Fn tsleep ,
>@@ -298,6 +276,28 @@
> .Va Giant
> mutex before the function returns.
> .Pp
>+.Ss Giant
>+Giant is a special instance of a sleep lock.
>+It has several special characteristics.
>+.Bl -enum
>+.It
>+It is recursive.
>+.It
>+Drivers can request that Giant be locked around them, but this is
>+going away.
>+.It
>+You can sleep while it has recursed, but other recursive locks cannot.
>+.It
>+Giant must be locked first before other locks.
>+.It
>+There are places in the kernel that drop Giant and pick it back up
>+again.
>+Sleep locks will do this before sleeping.
>+Parts of the Network or VM code may do this as well, depending on the
>+setting of a sysctl.
>+This means that you cannot count on Giant keeping other code from
>+running if your code sleeps, even if you want it to.
>+.El
> .Ss lockmanager locks
> Largely deprecated.
> See the
>@@ -325,11 +325,11 @@
> Lock order is important.
> .Pp
> .Em *2
>-readers can recurse though writers can not.
>+Readers can recurse though writers can not.
> Lock order is important.
> .Pp
> .Em *3
>-There are calls atomically release this primitive when going to sleep
>+There are calls to atomically release this primitive when going to sleep
> and reacquire it on wakeup (e.g.
> .Fn mtx_sleep ,
> .Fn rw_sleep
>@@ -340,7 +340,7 @@
> .Em *4
> Though one can sleep holding an sx lock, one can also use
> .Fn sx_sleep
>-which atomically release this primitive when going to sleep and
>+which will atomically release this primitive when going to sleep and
> reacquire it on wakeup.
> .Ss Context mode table.
> The next table shows what can be used in different contexts.
>@@ -363,7 +363,7 @@
> .Xr sleep 9 ,
> .Xr sx 9 ,
> .Xr LOCK_PROFILING 9 ,
>-.Xr WITNESS 9
>+.Xr witness 4
> .Sh HISTORY
> These
> functions appeared in

Actions: View | Diff

Attachments on bug 134074: 95643