From e69717d9e0cd107f461abff85f255be82d7bd69b Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Tue, 3 Sep 2019 18:07:28 +0000 Subject: Big wallclock/stopwatch refactor. It was long overdue. * --enable-clock and --enable-monotonic are gone * tain_sysclock() has been renamed tain_wallclock_read() * tain_wallclock_read() reads from CLOCK_REALTIME (or gettimeofday()) * tain_clockmon[_init]() have been renamed to tain_stopwatch_[read|init]() and now accept a monotonic clock name as an extra argument * tain_now() points to the system (wall) clock by default * tain_now_set_[stopwatch|wallclock]() can be used to switch Now to make a pass on all skarnet.org programs and add a tain_now_set_stopwatch() call everywhere needed... >.> --- doc/flags.html | 30 ------------------------------ 1 file changed, 30 deletions(-) (limited to 'doc/flags.html') diff --git a/doc/flags.html b/doc/flags.html index c901b1c..b74d344 100644 --- a/doc/flags.html +++ b/doc/flags.html @@ -175,36 +175,6 @@ and settimeofday() interfaces will be used. This is the default, and it's usually safe.

-

--enable-monotonic

- -

- Unless you have an accurate hardware system clock and you set it -on a linear time scale such as TAI-10 instead of UTC (see above), it is -generally a bad idea to trust the system clock for precise time interval -measurements. Single Unix recommends the use of clock_gettime() -with the CLOCK_MONOTONIC option to do such measurements: a stopwatch, not -a wall clock. However: -

- - - -

- If --enable-monotonic is set, then the absolute time given by the -tain_now() call will be computed with CLOCK_MONOTONIC. This -will ensure precise time arithmetic but may drift away from the system -clock. -

- -

- Otherwise, tain_now() will -return a time based on the system clock, and not use CLOCK_MONOTONIC. -This is the default. -

-

--disable-ipv6

-- cgit v1.3.1