Date: Thu, 04 Nov 2021 09:54:56 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 259642] CLOCK_* seems to default to CLOCK_*_PRECISE instead of CLOCK_*_FAST Message-ID: <bug-259642-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259642 Bug ID: 259642 Summary: CLOCK_* seems to default to CLOCK_*_PRECISE instead of CLOCK_*_FAST Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: 0mp@FreeBSD.org The clock_gettime(2) manual page [1] documents that: > The clock IDs CLOCK_REALTIME_FAST, CLOCK_MONOTONIC_FAST, > CLOCK_UPTIME_FAST are analogs of corresponding IDs without _FAST suffix > but do not perform a full time counter query, so their accuracy is one > timer tick. However, in the source code of kern_clock_gettime() in sys/kern/kern_time.c [2], the clock IDs without a suffix default to PRECISE instead of FAST. Is it the manual page or the source code that needs fixing? [1]: https://www.freebsd.org/cgi/man.cgi?query=clock_gettime&manpath=FreeBSD+13.0-RELEASE+and+Ports [2]: https://cgit.freebsd.org/src/tree/sys/kern/kern_time.c?h=releng%2F13.0#n323 -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-259642-227>