Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!rochester!sher
From: sher@rochester.UUCP (David Sher)
Newsgroups: net.arch,net.micro.mac,net.micro.68k
Subject: Re: timing loops
Message-ID: <15559@rochester.UUCP>
Date: Mon, 24-Feb-86 14:04:57 EST
Article-I.D.: rocheste.15559
Posted: Mon Feb 24 14:04:57 1986
Date-Received: Wed, 26-Feb-86 20:42:36 EST
References: <156@motatl.UUCP> <530@hoptoad.uucp> <2795@amdahl.UUCP>
Reply-To: sher@rochester.UUCP (David Sher)
Distribution: net
Organization: U. of Rochester, CS Dept.
Lines: 13
Keywords: timing loops
Xref: linus net.arch:2412 net.micro.mac:4835 net.micro.68k:1452

Just to introduce a theoretical note:
Wouldn't an entirely self timed architecture avoid the issue of
software timing loops?  I would think that this would put the problem
where it belongs, in the hardware.  Of course you pay a certain factor
for self timing (I think it depends on the size of the chunks of hardware
that are self timed).  

Probably this has no relevance to current real machines but I'm an academic
anyway.
-- 
-David Sher
sher@rochester
seismo!rochester!sher