Every so often I get a call from someone who wants to know the gate count (or equivalently, the silicon area) of some embedded processor core. And every time this happens, I have to stifle the urge to say “Why on earth do you care?”
The reason the question baffles me is that, in chips that use embedded processor cores, the area used by the core is almost always negligible compared to the area eaten up by memory banks. It’s common for the processor core to consume only about 10% of the die area, with 60-80% consumed by memory. Thus, in typical embedded chips, the size of the core itself is just not that significant in determining overall chip size.
“But wait,” you say. “Isn’t it important to choose a core that helps to minimize chip size (and hence cost)?” Absolutely. But comparing gate counts isn’t the best way to go about making this choice. A better metric to use for this purpose is processor memory efficiency.
Memory efficiency measures how much memory is required for the core to execute a given task. It includes both program (instruction) and data memory. The core’s architecture and instruction set exert a direct influence on its memory efficiency; the quality of the compiler can also play a critical role if portions of the application are written in a high-level language.
Because embedded chip size tends to be dominated by on-chip memory, the size of memory required by the core has a dramatic impact on the overall chip size—a greater impact than the size of the core itself. To illustrate this concept, imagine that Core A is 50% smaller than Core B, but uses 30% more memory. Assuming that with Core B the chip has an 8:1 ratio of memory area to core area, it turns out that the bigger core will yield a smaller chip. Of course, the chip designer can always skimp on memory to make the chip smaller, but then the system designer has to make up for it by adding off-chip memory banks. This can increase system cost and energy consumption and reduce system reliability.
As prospective core licensees become more aware of the importance of memory usage, perhaps core vendors will spend less effort promoting their svelte gate counts and more effort promoting the attributes that really count.
Add new comment