Page Menu
Home
FreeBSD
Search
Configure Global Search
Log In
Files
F154363829
D11142.diff
No One
Temporary
Actions
View File
Edit File
Delete File
View Transforms
Subscribe
Mute Notifications
Flag For Later
Award Token
Size
2 KB
Referenced Files
None
Subscribers
None
D11142.diff
View Options
Index: head/share/man/man4/dtrace_lockstat.4
===================================================================
--- head/share/man/man4/dtrace_lockstat.4
+++ head/share/man/man4/dtrace_lockstat.4
@@ -24,7 +24,7 @@
.\"
.\" $FreeBSD$
.\"
-.Dd June 9, 2017
+.Dd June 11, 2017
.Dt DTRACE_LOCKSTAT 4
.Os
.Sh NAME
@@ -61,7 +61,7 @@
provider contains DTrace probe for inspecting the kernel's lock
state transitions.
Tracepoints exist for several types of kernel
-locking primitives, including mutexes, spin, reader-writer,
+locking primitives, including mutexes, spin, reader-writer,
and shared exclusive locks.
An attempt has been made to provide a regular and easy to understand
interface to the
@@ -101,7 +101,7 @@
the lock and the second argument is the length of time,
in nanoseconds,
that the waiting thread was blocked.
-The
+The
.Fn lockstat:::adaptive-block
probe fires only after the lock has been successfully acquired,
after the adaptive-acquire probe fires.
@@ -144,13 +144,13 @@
in nanoseconds,
that the waiting thread was blocked.
The third argument is 1 if the thread was were spinning while
-trying to acquire a read lock,
+trying to acquire a read lock,
otherwise it will be 0 indicating that we were spinning for the write lock.
The fourth argument is 1 if we were waiting for a reader to release the lock,
-otherwise it will be 0 indicating that we were waiting for a writer
+otherwise it will be 0 indicating that we were waiting for a writer
to release the lock.
-The fifth argument is the number of readers that held the lock when
-we started spinning; in particular, argument 5 is non-zero only
+The fifth argument is the number of readers that held the lock when
+we started spinning; in particular, argument 5 is non-zero only
if the fourth argument is 1.
.Pp
The
@@ -195,13 +195,13 @@
in nanoseconds,
that the waiting thread was blocked.
The third argument is 1 if the thread was were spinning while
-trying to acquire a read lock,
+trying to acquire a read lock,
otherwise it will be 0 indicating that we were spinning for the write lock.
The fourth argument is 1 if we were waiting for a reader to release the lock,
-otherwise it will be 0 indicating that we were waiting for a writer
+otherwise it will be 0 indicating that we were waiting for a writer
to release the lock.
-The fifth argument is the number of readers that held the lock when
-we started spinning; in particular, argument 5 is non-zero only
+The fifth argument is the number of readers that held the lock when
+we started spinning; in particular, argument 5 is non-zero only
if the fourth argument is 1.
.Pp
The
@@ -237,7 +237,7 @@
.Xr dtrace 1 ,
.Xr lockstat 1 ,
.Xr locking 9 ,
-.Xr SDT 9 ,
+.Xr SDT 9
.Sh HISTORY
The
.Nm lockstat
File Metadata
Details
Attached
Mime Type
text/plain
Expires
Wed, Apr 29, 3:10 AM (18 h, 22 m)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
32320747
Default Alt Text
D11142.diff (2 KB)
Attached To
Mode
D11142: Tidy up minor nits raised by mandoc lint in dtrace_lockstat(4)
Attached
Detach File
Event Timeline
Log In to Comment