Breaking News
Blog

Asynchronous Techniques Push Moore's Law to the Physical Limit

Page 1 / 2 Next >
View Comments: Newest First | Oldest First | Threaded View
<<   <   Page 4 / 7   >   >>
Garcia-Lasheras
User Rank
Blogger
Re: Moore's law.....
Garcia-Lasheras   2/14/2014 9:09:28 AM
NO RATINGS
@David: "True, the transistors you can fit in one layer are getting limited, but we're still putting more transistors on a chip by putting in more layers"

Yes, this is true. But this increases the issues related to clock distribution problems too!!

In state-of-the-art digital ICs, as much as the 50% of power consumption is drawn by the clock distribution circuitry in order to assure that the signal will be "skew-free" across the whole layout. This is because we need to include lots of "H" forks and signal buffers for getting a clear signal.

When we jump to a extra 3rd dimension, this problem gets worse, as illustrated in the next image -- shared from the Ecole Polythecnique Federale de Lausanne (link):



 

 

 

jackOfManyTrades
User Rank
Manager
Re: I never metastable I liked
jackOfManyTrades   2/14/2014 9:08:03 AM
NO RATINGS
Interesting - did you design all the ICs as well as the PCB?

I'm coming at this as an ex-digital IC designer (65nm was considered sexy when I stopped). I was designing standard components, which customers could take and use as they wished. From that point of view, once signals left the IC, all bets were off: not only did I not have any control over the customer's PCB layout, I didn't know what other ICs they might be using.

betajet
User Rank
CEO
Re: I never metastable I liked
betajet   2/14/2014 9:01:40 AM
NO RATINGS
Jack wrote: The chips on a PCB will probably all be synchronous designs, but they certainly won't all be sharing the same clock tree!

Actually, they may be sharing a single PLL-based clock generator that derives all the clocks from a single reference.  In that case they are sharing the same clock tree, with the trunks implemented on the PCB and the branches inside different ICs.  For example, one of my designs has a 33.333 MHz master clock with matched clock lines so that the clock arrives at the various ICs and I/O modules at the same time.  Very clean, plenty of timing margin.

Garcia-Lasheras
User Rank
Blogger
Re: I never metastable I liked
Garcia-Lasheras   2/14/2014 8:54:52 AM
NO RATINGS
@Betajet: "Aren't you going to have metastability problems with multiple clock islands?"

Metastability is a real issue in all asynchronous logic designs, just as it is in synchronous designs dealing with asynchronous external inputs.

About the synchronous islands, let me clarify that having such designs blocks doesn't always mean you are using a conventional periodic clock. The synchronous island implies that you have a local clock distribution network that acts as an "isochronic fork". This is, by limiting the clock network to a local boundary, you can assure that you can insert a clock/trigger signal in the clock network input and this signal will reach the local registers/flip-flops with a controlled skew inside the synchronous island. By this way, you can use conventional synchronous EDA tools in order to design, synthesize and lay down the digital logic inside the island.

But the point is that the "clock" you are injecting into such a local synchronous island may be a locally generated signal, being aligned by this way with the asynchronous handshaking control circuitry. This is what is called a "pausable clock", and it supposes an advantage in power consumption as this is only tiriggering when the synchronous logic block has an actual work to do.

jackOfManyTrades
User Rank
Manager
Re: I never metastable I liked
jackOfManyTrades   2/14/2014 4:15:37 AM
NO RATINGS
This GALS idea seems to be just using a similar approach on a chip that is tradionally used on a PCB. The chips on a PCB will probably all be synchronous designs, but they certainly won't all be sharing the same clock tree!

Paul A. Clayton
User Rank
CEO
Re: I love asynchronous logic
Paul A. Clayton   2/13/2014 9:29:55 PM
NO RATINGS
Asynchronous design is interesting at various scales, but I also find wave pipelining interesting (which is sort of related to timing-dependent asynchronous design). It seems neat that one can avoid a pipeline latch by timing more pulse-like signals (waves) such that they do not overlap. Sadly, wave pipelining is a victim of fast clocks, process variation, and other modern factors.

David Ashton
User Rank
Blogger
Re: Moore's law.....
David Ashton   2/13/2014 8:59:29 PM
NO RATINGS
@Alex-m1.....by the time we run out of that, someone will have thought of something else....  :-)

alex_m1
User Rank
CEO
Re: Moore's law.....
alex_m1   2/13/2014 8:48:54 PM
NO RATINGS
Most likely 3d chips will buy us 1-2 or maybe 3 generations of moore's law(both in density and partially in price). After that prices won't go down(according to zvi orbach from monolitic 3d), and it would be hard to put more layers due to thermal limits.

David Ashton
User Rank
Blogger
Re: I never metastable I liked
David Ashton   2/13/2014 8:00:46 PM
NO RATINGS
@betajet I must admit that occurred to me as well.  Back in the day I used to deal with strings of modems used to poll terminals.  You HAD to have one clock through the whole system or you'd get errors.  If anything puts data out faster than something else can accept it, you'll start losing it.  You can use buffers to take up phase differences and slight clock slippage but eventually the buffer will over- or under-flow.

If your buffer is big enough and you're only sending bursts of data you can get away with differences, but we're talking big amounts of data here I think?

David Ashton
User Rank
Blogger
Moore's law.....
David Ashton   2/13/2014 7:52:49 PM
NO RATINGS
tpfj wrote: "Moore himself wrote only about the density of components (or transistors)".

Based on that, and the impending proliferation of 3D ICs, are we not extending Moore's law vertically, so to speak?  True, the transistors you can fit in one layer are getting limited, but we're still putting more transistors on a chip by putting in more layers.

Max - you're an expert on this, what do you think?

<<   <   Page 4 / 7   >   >>
Top Comments of the Week
August Cartoon Caption Winner!
August Cartoon Caption Winner!
"All the King's horses and all the KIng's men gave up on Humpty, so they handed the problem off to Engineering."
5 comments
Like Us on Facebook

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)
EE Times on Twitter
EE Times Twitter Feed
Radio
LATEST ARCHIVED BROADCAST
David Patterson, known for his pioneering research that led to RAID, clusters and more, is part of a team at UC Berkeley that recently made its RISC-V processor architecture an open source hardware offering. We talk with Patterson and one of his colleagues behind the effort about the opportunities they see, what new kinds of designs they hope to enable and what it means for today’s commercial processor giants such as Intel, ARM and Imagination Technologies.
Flash Poll