Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!samsung!uakari.primate.wisc.edu!ames!dftsrv!mimsy!chris
From: chris@mimsy.umd.edu (Chris Torek)
Newsgroups: comp.unix.wizards
Subject: Re: Real-Time Granularity: A Query
Message-ID: <21287@mimsy.umd.edu>
Date: 14 Dec 89 22:57:14 GMT
References: <598@codonics.COM>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 15

In article <598@codonics.COM> bret@codonics.COM (Bret Orsburn) writes:
>The gettimeofday function returns (in part) a microsecond resolution counter.
>The docs I have found so far indicate that this counter is really just bumped
>by the system tick interrupt at a 50-100 HZ rate. Is that a useful
>generalization? Are there any significant counter-examples?

No, and yes (in that order): 4.3BSD on most VAXen, for instance.  These
have a 100 hz clock, but can read the countdown (acutally count-up) register
to tell how long it has been since the last clock interrupt, and there
is a routine called microtime() that calculates the time to the nearest
microsecond or so.  Of course, by the time the time has been calculated,
it is wrong again. . . .
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@cs.umd.edu	Path:	uunet!mimsy!chris