From owner-freebsd-hackers Wed Jun 18 04:24:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA11560 for hackers-outgoing; Wed, 18 Jun 1997 04:24:08 -0700 (PDT) Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA11553 for ; Wed, 18 Jun 1997 04:24:06 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id FAA19300; Wed, 18 Jun 1997 05:24:03 -0600 (MDT) Message-Id: <199706181124.FAA19300@pluto.plutotech.com> To: Simon Shapiro cc: FreeBSD-Hackers@FreeBSD.ORG Subject: Re: High Resolution Timers, How? In-reply-to: Your message of "Wed, 18 Jun 1997 01:33:55 PDT." Date: Wed, 18 Jun 1997 06:22:47 -0600 From: "Justin T. Gibbs" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Hi Y'all, > >I am in need for a precise, high resolution timer within the kernel. >I need it to time certain instructions, functions, and I/O events. If you only need high resolution "time of day" functionality, use microtime(). >The best i could find is a global variable called time which claims >to have a usec resolution but; Either I am exceptionally lucky and >always hit it on a x000000 resolution, or it is not telling the >truth. i need a timer that will increment in usec resolution or >as close to it as I can get. Were you looking at lbolt? -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================