Date: Sat, 29 Oct 2005 09:59:52 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: PeterJeremy@optushome.com.au Cc: phk@phk.freebsd.dk, rwatson@freebsd.org, current@freebsd.org Subject: Re: Timers and timing, was: MySQL Performance 6.0rc1 Message-ID: <20051029.095952.29330299.imp@bsdimp.com> In-Reply-To: <20051029084716.GY39882@cirb503493.alcatel.com.au> References: <20051029005719.I20147@fledge.watson.org> <37685.1130571501@critter.freebsd.dk> <20051029084716.GY39882@cirb503493.alcatel.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20051029084716.GY39882@cirb503493.alcatel.com.au>
Peter Jeremy <PeterJeremy@optushome.com.au> writes:
: Most applications will do all their timekeeping using a single set of
: clock calls so I don't think this is especially serious. Does POSIX
: require any guarantees about (eg) clock_gettime(CLOCK_REALTIME), time()
: and gettimeofday() returning identical values? Can we claim "rounding
: and truncation" to explain the discrepancies?
I'm not sure that most of them do. I've seen all three used in the
libraries we have at work, for example. It would be nice if the
inaccuracies were well documented...
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051029.095952.29330299.imp>