Issues For Architects
Thursday, April 30th, 2009Power may be a persistent issue for semiconductor design, but for many companies it’s still not part of the architectural decision.
This may seem rather odd, considering that at 65nm and below power is an issue in all chips, along with lithography, insulation, on-chip interfaces and packaging. In fact, power is a myriad of issues ranging from static and dynamic leakage to power islands, signal integrity and gate structures. Yet many architects still don’t see it as their issue.
That likely will change over the next couple of years, as the leading edge of design heads to 32nm (and/or 28nm). Power will become even more pressing than it has been, with power islands, timing and various sleep, wake, on and off modes rising to center stage into a design. Over the next two generations of chips, architects will have to consider everything from reducing margins to get better power optimization to new materials and structures. They’re going to have to plan up front for how chips can be verified, including low-power IP, and they’re going to need to understand whether a chip can be manufactured with sufficient yield to make it economically viable.
These are big changes on the architecture side. Add to that more functionality, more dictates from the people wearing suits about what functions need to be included and what gets priority, and cost analyses about which nodes are next and which ones may be skipped and the life of an architect begins getting significantly less independent than in the past.
For the better part of a decade we have witnessed convergence of functions on a chip, and for the past two decades we have seen some of that convergence within end-user devices. Beyond 45nm, there is so much space to use on a chip that more and more functions can be built into it. Intel already has begun adding graphics engines into its processors, and most cell phone makers expect GPS will be standard on smart phones within the next couple years.
Batteries will have to last long enough to make those additional functions useful, and they will have to work in accordance with priorities set by consumers and businesses. That means changes in software, changes in design, and all of it has to begin at the architecture level. It also means that the convergence that has occurred on the technology side will lead to convergence on the people side, where more and more people are involved at the architectural level rather than at the next stage down.
A word of advice to chip architects: Book the bigger conference room next time.
–Ed Sperling
