summaryrefslogtreecommitdiffstats
path: root/share
diff options
context:
space:
mode:
authormarkm <markm@FreeBSD.org>2000-09-25 11:18:51 +0000
committermarkm <markm@FreeBSD.org>2000-09-25 11:18:51 +0000
commit6402d3f40ea56505f1daf2bf646a4e4662bd7d24 (patch)
treeb0bf1d93e1fdac8ef143647fd1ed90019023fcff /share
parentdddc67f9130b7b6d79919c1341fdfa5a5c4fe5c4 (diff)
downloadFreeBSD-src-6402d3f40ea56505f1daf2bf646a4e4662bd7d24.zip
FreeBSD-src-6402d3f40ea56505f1daf2bf646a4e4662bd7d24.tar.gz
Remove references to the defunct kern.timecounter.method sysctl variable.
Diffstat (limited to 'share')
-rw-r--r--share/man/man9/microuptime.916
1 files changed, 1 insertions, 15 deletions
diff --git a/share/man/man9/microuptime.9 b/share/man/man9/microuptime.9
index 69a2487..d8b2f8c 100644
--- a/share/man/man9/microuptime.9
+++ b/share/man/man9/microuptime.9
@@ -69,19 +69,8 @@ Whereas
.Fn getmicrouptime
and
.Fn getnanouptime
-functions are abstractions which can alternately return a less precise, but
+functions are abstractions which return a less precise, but
faster to obtain, time.
-This behaviour can be toggled via the
-kern.timecounter.method sysctl variable:
-.Bl -tag -width ABC
-.It Dv 0
-sacrifice precision in favor of faster code execution
-.It Dv 1
-return the more precise time (the same as calling
-.Fn microuptime
-or
-.Fn nanouptime ) .
-.El
.Pp
The intent of the
.Fn getmicrouptime
@@ -95,9 +84,6 @@ execution time.
.Xr microtime 9 ,
.Xr nanotime 9 ,
.Xr tvtohz 9
-.Sh DIAGNOSTICS
-Buggy hardware can cause "calcru negative..." when kern.timecounter.method
-is set to 0.
.Sh AUTHORS
This manual page was written by
.An Kelly Yancey Aq kbyanc@posi.net .
OpenPOWER on IntegriCloud