Date: Fri, 28 Oct 2005 16:16:22 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: David Xu <davidxu@freebsd.org> Cc: Pertti Kosunen <pertti.kosunen@pp.nic.fi>, ticso@cicely.de, "Yuriy N. Shkandybin" <jura@networks.ru>, current@freebsd.org Subject: Re: Timers and timing, was: MySQL Performance 6.0rc1 Message-ID: <32650.1130508982@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 28 Oct 2005 21:25:03 %2B0800." <436226AF.10109@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <436226AF.10109@freebsd.org>, David Xu writes: >That's just an idea. :-) >As robert said, add a lower resolution CLOCK_ type may work well. >Another thing I just though of, if reading timercounter is so slow, won't >gettimeofday hardly block cpu too many cycles ? the cpu is just stucked >there by a slow clock in hardware signals. The get*() family of functions just copy a timestamp, they go nowhere near hardware. So they are fast, but less precise (~ 1 msec). -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32650.1130508982>