SoC Architecture: NVIDIA's Denver CPU

It admittedly does a bit of a disservice to the rest of the Nexus 9 both in terms of hardware and as a complete product, but there’s really no getting around the fact that the highlight of the tablet is its NVIDIA-developed SoC. Or to be more specific, the NVIDIA-developed Denver CPUs within the SoC, and the fact that the Nexus 9 is the first product to ship with a Denver CPU.

NVIDIA for their part is no stranger to the SoC game, now having shipped 5 generations of Tegra SoCs (with more on their way). Since the beginning NVIDIA has been developing their own GPUs and then integrating those into their Tegra SoCs, using 3rd party ARM cores and other 1st party and 3rd party designs to fully flesh out Tegra. However even though NVIDIA is already designing some of their own IP, there’s still a big leap to be made from using licensed ARM cores to using your own ARM cores, and with Denver NVIDIA has become just the second company to release their own ARMv8 design for consumer SoCs.

For long time readers Denver may feel like a long time coming, and that perception is not wrong. NVIDIA announced Denver almost 4 years ago, back at CES 2011, where at the time they made a broad announcement about developing their own 64bit ARM core for use in wide range of devices, ranging from mobile to servers. A lot has happened in the SoC space since 2011, and given NVIDIA’s current situation Denver likely won’t be quite as broad a product as they first pitched it as. But as an A15 replacement for the same tablet and high performance embedded markets that the TK1-32 has found a home in, the Denver-based TK1-64 should fit right in.


K1-64 Die Shot Mock-up (NVIDIA)

Denver comes at an interesting time for NVIDIA and for the ARM SoC industry as a whole. Apple’s unexpected launch of the ARMv8 capable Cyclone core in 2013 beat competing high-performance ARMv8 designs by nearly a year. And overall Apple set a very high bar for performance and power efficiency that is not easily matched and has greatly impacted the development and deployment schedules of other ARMv8 SoCs. At the same time because Cyclone and its derivatives are limited to iOS devices, the high-performance Android market is currently served by a mix of ARMv7 designs (A15, Krait, etc) and the just recently arrived A57 and Denver CPUs.

Showcasing the full scope of the ARM architecture license and how many different designs can execute the same instruction set, none of these ARMv8 CPUs are all that much alike. Thanks to its wide and conservatively clocked design, Apple’s Cyclone ends up looking a lot like what a recent Intel Core processor would look like if it were executing ARM instead of x86. Meanwhile ARM’s A57 design is (for lack of a better term) very ARMy, following ARM’s own power efficient design traditions and further iterating on ARM’s big.LITTLE philosophy to pair up high performance A57 and moderate performance A53 cores to allow a SoC to cover a wide power/performance curve. And finally we have Denver, perhaps the most interesting and certainly least conventional design, forgoing the established norms of Out of Order Execution (OoOE) in favor of a very wide in-order design backed by an ambitious binary translation and optimization scheme.

Counting Cores: Why Denver?

To understand Denver it’s best to start with the state of the ARM device market, and NVIDIA’s goals in designing their own CPU core. In the ARM SoC space, much has been made of core counts, both as a marketing vehicle and of value to overall performance. Much like the PC space a decade prior, when multi-core processors became viable they were of an almost immediate benefit. Even if individual applications couldn’t yet make use of multiple cores, having a second core meant that applications and OSes were no longer time-sharing a single core, which came with its own performance benefits. The OS could do its work in the background without interrupting applications as much, and greedy applications didn’t need to fight with the OS or other applications for basic resources.

However also like the PC space, the benefits of additional cores began to taper off with each additional core. One could still benefit from 4 cores over 2 cores, but unless software was capable of putting 3-4 cores to very good use, generally one would find that performance didn’t scale well with the cores. Compounding matters in the mobile ecosystem, the vast majority of devices run apps in a “monolithic” fashion with only one app active and interacting with the user at any given point in time. This meant that in absence of apps that could use 3-4 cores, there weren’t nearly as many situations in which multitasking could be employed to find work for the additional cores. The end result has been that it has been difficult for mobile devices to consistently saturate an SoC with more than a couple of cores.

Meanwhile the Cortex family of designs coming from ARM have generally allowed high core counts. Cortex-A7 is absolutely tiny, and even the more comparable Cortex-A15 isn’t all that big on the 28nm process. Quad core A15 designs quickly came along, setting the stage for the high core count situations we previously discussed.

This brings us to NVIDIA’s goals with Denver. In part due to the issues feeding 4 cores, NVIDIA has opted for a greater focus on single-threaded performance than the ARM Cortex designs they used previously. Believing that fewer, faster cores will deliver better real-world performance and better power consumption, NVIDIA set out to build a bigger, wider CPU that would do just that. The result of this project was what NVIDIA awkwardly calls their first “super core,” Denver.

Though NVIDIA wouldn’t know it at the time it was announced in 2011, Denver in 2015 is in good company that helps to prove that NVIDIA was right to focus on single-threaded performance over additional cores. Apple’s Cyclone designs have followed a very similar philosophy and the SoCs utilizing them remain the SoCs to beat, delivering chart-topping performance even with only 2 or 3 CPU cores. Deliver something similar in performance to Cyclone in the Android market and prove the performance and power benefits of 2 larger cores over 4 weaker cores, and NVIDIA would be well set in the high-end SoC marketplace.

Performance considerations aside, for NVIDIA there are additional benefits to rolling their own CPU core. First and foremost is that it reduces their royalty rate to ARM; ARM still gets a cut as part of their ISA license, but that cut is less than if you are also using ARM licensed cores. The catch of course is that NVIDIA needs to sell enough SoCs in the long run to pay for the substantial costs of developing a CPU, which means that along with the usual technical risks, there are some financial risks as well for developing your own CPU.

The second benefit to NVIDIA then is differentiation in a crowded SoC market. The SoC market has continued to shed players over the years, with players such as Texas Instruments and ST-Ericsson getting squeezed out of the market. With so many vendors using the same Cortex CPU designs, from a performance perspective their SoCs are similarly replaceable, making the risk of being the next TI all the greater. Developing your own CPU is not without risks as well – especially if it ends up underperforming the competition – but played right it means being able to offer a product with a unique feature that helps the SoC stand out from the crowd.

Finally, at the time NVIDIA announced Denver, NVIDIA also had plans to use Denver to break into the server space. With their Tesla HPC products traditionally paired x86 CPUs, NVIDIA could never have complete control over the platform, or the greater share of revenue that would entail. Denver in turn would allow NVIDIA to offer their own CPU, capturing that market and being able to play off of the synergy of providing both the CPU and GPU. Since then however the OpenPOWER consortium happened, opening up IBM’s POWER CPU lineup to companies such as NVIDIA and allowing them to add features such as NVLink to POWER CPUs. In light of that, while NVIDIA has never officially written off Denver’s server ambitions, it seems likely that POWER has supplanted Denver as NVIDIA’s server CPU of choice.

Introduction Designing Denver
POST A COMMENT

169 Comments

View All Comments

  • UtilityMax - Sunday, February 15, 2015 - link

    I don't fully understand you comment about the SoC? You think web browser is using the hardware somewhat differently from the dedicated apps?

    My comment is about the fact that there is not point to have most of the dedicated apps when you have a tablet with a screen the size of a small laptop or netbook. Just fire up the web browser and use whatever web site you need. Most dedicated mobile apps exist because the screen size of a cell phone is pretty small, which can make for an awkward experience even when you pull a mobile web site though a web browser.
    Reply
  • UtilityMax - Sunday, February 8, 2015 - link

    It's not entirely true that there isn't much in the tablet space, besides Nexus 9 and Galaxy Tab S. If your pockets are deep enough, you could always get the Apple iPad Air 2. Apple gives you a well balanced tablet with great build quality, fine screen, CPU/GPU performance, and battery life. The only thing that's missing is an SD card slot, but at least there is an option a 64 or 128GB model. Personally, I ended buying a Tab S 10.5 because it was truly difficult to resist it at only $400 sale price, plus $35 for a 64GB SD card. Despite all the disappointing benchmarks, Tab S provides a pretty smooth and fluid android experience with a great screen. Battery life is the only thing that's getting on the way. Five hours of web browsing or standby is pretty disappointing. Reply
  • wintermute000 - Monday, February 9, 2015 - link

    Sony Xperia Tablet Z2. SoC is one gen behind but if you can get it for a good price, you're laughing. Fantastic build, clean stock software, lag free. Reply
  • sunil5228 - Sunday, February 8, 2015 - link

    Brilliant ! Esp loved the segway into the Denver CPU and dual vs quad arcitechture comparisons,very eye opening. thankyou sir Reply
  • bdiddytampa - Wednesday, February 11, 2015 - link

    Picked one of these up a couple weeks ago and love it. It performs phenomenally well, and looks great. It's a bit heavy for its size and the thin bezel on the sides makes it difficult to hold with one hand without touching the screen, but overall its a fantastic tablet. Highly recommend it. Reply
  • Ozo - Monday, February 16, 2015 - link

    Thanks for the lucid explanation of Denver.

    Any insight into why Google/HTC dropped the ball on "wireless" Qi charging? Especially when it was finally added to the Nexus phone!?!

    I was set to upgrade from my Nexus 7 (2013), but no Qi = no sale. :(
    Reply
  • Fardreit - Monday, February 23, 2015 - link

    I'll be honest: I don't understand 80% of what the reviewer wrote. But the 20% that I do understand is enough for me to appreciate the conclusions drawn. I value the informed reviews here much more than those at the 'fan' websites. At Anandtech, people really know what they're talking about, even if I don't.

    When I'm able to follow the high-tech insults you guys sling at each other, then I know I've made progress.
    Reply
  • flashbacck - Wednesday, February 25, 2015 - link

    Does the Shield Tablet use a similar DCO? I have noticed during it has performance issues during regular use. I wonder if it's this DCO that still needs work. Reply
  • ahcox - Thursday, February 25, 2016 - link

    What is the accuracy of the image labelled "K1-64 Die Shot Mock-up"? Is it a colorized and enhanced version of a real die photograph or is it a pure invention? That 16 * 12 array dominating the picture seems a little off to me: surely there should be structures common to each 16*2 group forming an SMX? Kepler is not a simple tiled sea of cores. Reply

Log in

Don't have an account? Sign up now