Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site hoptoad.uucp
Path: utzoo!linus!decvax!decwrl!sun!hoptoad!gnu
From: gnu@hoptoad.uucp (John Gilmore)
Newsgroups: net.arch
Subject: Re: timing loops
Message-ID: <535@hoptoad.uucp>
Date: Tue, 18-Feb-86 19:31:56 EST
Article-I.D.: hoptoad.535
Posted: Tue Feb 18 19:31:56 1986
Date-Received: Thu, 20-Feb-86 00:00:40 EST
References: <156@motatl.UUCP> <530@hoptoad.uucp> <2795@amdahl.UUCP>
Organization: Nebula Consultants in San Francisco
Lines: 18

In article <2795@amdahl.UUCP>, mat@amdahl.UUCP (Mike Taylor) writes:
> In article <530@hoptoad.uucp>, gnu@hoptoad.uucp (John Gilmore) writes:
> >                        Give me a good way to wait 2.2us *without*
> > depending on instruction timing, and I'll consider your request.
>
> Well, on a *real* computer, you just set the TOD clock comparator for
> now+2.2 us. and go do something useful while you wait.  Sorry, couldn't
> resist.

I didn't think you could do anything useful in 100 System/370
instructions anyway.  In fact, it probably takes more than that to set
the clock comparator (timer queues ya know).  Sorry, didn't resist.

Something like the System/370 TOD clock and comparator is the kind of
facility I was talking about, though: a standard, high precision clock
that doesn't change regardless of what system model you have.
-- 
John Gilmore  {sun,ptsfa,lll-crg,ihnp4}!hoptoad!gnu   jgilmore@lll-crg.arpa