Path: utzoo!utgpu!water!watmath!clyde!rutgers!gatech!hubcap!ncrcae!ncr-sd!hp-sdd!hplabs!hpda!hpsmtc1!hpisod2!hpsel1!hpindda!vandys
From: vandys@hpindda.HP.COM (Andy Valencia)
Newsgroups: comp.arch
Subject: Re: Cycle stretching
Message-ID: <3450002@hpindda.HP.COM>
Date: 17 Feb 88 17:29:38 GMT
References: <844@daisy.UUCP>
Organization: HP Information Networks, Cupertino, CA
Lines: 27


	If you're going to do this, why not take it all the way and
make your computer "event driven" instead of clocked?  Then your
computation can continue at the highest speed available from your
components (gee, and you could even replace slow components with faster
ones....)

	So an "add register to memory" would go like:

Events		Sequencer
		<Request register #x>
		<Request memory location #N>
<Register x>
<Mem N>
		... pipline in: <Request next instr location>
		<Request ADD>
<ADD done>
		<Request write memory location #N>
... <Next instr>
		... start next instruction
<Write done>

	Bunches of asynchronously executing components... I wonder
what it would be like to diagnose the microcode :-<.

			Andy Valencia
			vandys%hpindda.UUCP@hplabs.hp.com