NVIDIA Demonstrates Logan SoC: < 1W Kepler, Shipping in 1H 2014, More Energy Efficient than A6X?by Anand Lal Shimpi on July 24, 2013 9:00 AM EST
Ever since its arrival in the ultra mobile space, NVIDIA hasn't really flexed its GPU muscle. The Tegra GPUs we've seen thus far have been ok at best, and in serious need of improvement at worst. NVIDIA often blamed an immature OEM ecosystem unwilling to pay for the sort of large die SoCs necessary in order to bring a high-performance GPU to market. Thankfully, that's all changing. Earlier this year NVIDIA laid out its mobile SoC roadmap through 2015, including the 2014 release of Project Logan - the first NVIDIA ultra mobile SoC to feature a Kepler GPU. Yesterday in a private event at Siggraph, NVIDIA demonstrated functional Logan silicon for the very first time.
NVIDIA got Logan silicon back from the fabs around 3 weeks ago, making it almost certain that we're dealing with some form of 28nm silicon here and not early 20nm samples.
NVIDIA isn't talking about CPU cores, but it's safe to assume that Logan will be another 4+1 arrangement of cores - likely still based on ARM's Cortex A15 IP (but perhaps a newer revision of the core). On the GPU front, NVIDIA confirmed our earlier speculation that Logan includes a single Kepler SMX:
One Kepler SMX features 192 CUDA cores. NVIDIA isn't talking about shipping GPU frequencies either, but it did provide this chart to put Logan's GPU capabilities into perspective:
Don't get too excited as we're looking at a comparison of GFLOPS and not game performance, but the peak theoretical ALU bound performance of mobile Kepler should exceed that of a Playstation 3 or GeForce 8800 GTX (memory bandwidth is another story however). If we look closely at NVIDIA's chart and compare mobile Kepler to the iPad 4, we get a better idea of what sort of clock speeds NVIDIA would need to attain this level of performance. Doing some quick Photoshop estimation it looks like NVIDIA is claiming mobile Kepler has somewhere around 5.2x the FP power of the PowerVR SGX 554MP4 in the iPad 4 (76.8 GFLOPS). That works out to be right around 400 GFLOPS. With a 192 core implementation of Kepler, you get 2 FLOPS per core or 384 FLOPS per cycle. To hit 400 GFLOPS you'd need to clock the mobile Kepler GPU at roughly 1GHz. That's certainly doable from an architectural standpoint (although we've never seen it done on any low power 28nm process), but it's probably a bit too high for something like a smartphone.
NVIDIA didn't want to talk frequencies but they did tell me that we might see something this fast in some sort of a tablet. I suspect that most implementations will be clocked significantly lower. Even at half the frequency though, we're still talking about roughly Playstation 3 levels of FP power out of a mobile SoC. We know nothing of Logan's memory subsystem, which obviously plays a major role in real world gaming performance but there's no getting around the fact that Logan's Kepler implementation means serious business. For years we've lamented NVIDIA's mobile GPUs, Logan looks like it's finally going to change that.
API Support and Live Demos
Unlike previous Tegra GPUs, Kepler is a fully unified architecture and OpenGL ES 3.0, OpenGL 4.4 and DirectX 11 compliant. The API compliance alone is a huge step forward for NVIDIA. It's also a big one for game developers looking to move more seriously into mobile. Epic's Tim Sweeney even did a blog post for NVIDIA talking about Logan's implementation of Kepler and how it brings feature parity between PCs, next-gen consoles and mobile platforms. NVIDIA responded in kind by running some Unreal Engine 4 demos on Android on a Logan test platform. That's really the big story behind all of this. With Logan, NVIDIA will bring its mobile GPUs up to feature parity with what it's shipping in the PC market. Game developers looking to port games between console, PC, tablet and smartphone should have an easier job of doing that if all platforms supported the same APIs. Logan will take NVIDIA from being very behind in API support (with no OpenGL ES 3.0 support) to the head of the class.
NVIDIA took its Ira demo, originally run on a Titan at GTC 2013, and got it up and running on a Logan development board. Ira did need some work to make the transition to mobile. The skin shaders were simplified, smaller textures are used and the rendering resolution is dropped to 1080p. NVIDIA claims this demo was done in a 2 - 3W power envelope.
The next demo is called Island and was originally shown on a Fermi desktop part. Running on Logan/mobile Kepler, this demo shows OpenGL 4.3 and hardware tessellation working.
The development board does feature a large heatspreader, but that's not too unusual for early silicon just out of bring up. Logan's package size should be comparable to Tegra 4, although the die size will clearly be larger. The dev board is running Android and is connected to a 10.1-inch 1920 x 1200 touchscreen.
Post Your CommentPlease log in or sign up to comment.
View All Comments
cdripper2 - Wednesday, July 24, 2013 - linkthat was @ ExarKun333. post didn't work quite right there....
Concillian - Wednesday, July 24, 2013 - linkThis is great news. Feature parity with PCs is enormous. Should be great for nVidia, and likely very bad news for PowerVR.
Stuka87 - Wednesday, July 24, 2013 - linkGlad to see them ditch Tegra, which was outdated the day it was released. performance numbers should go way up with the Qualcomm chip.
Stuka87 - Wednesday, July 24, 2013 - linkarg, wrong window, ignore my last comment :/
michael2k - Wednesday, July 24, 2013 - linkExcept PowerVR Series 6 is essentially at parity, and was available for licensing last January and should be shipping this year. Logan isn't supposed to be out until next year.
HisDivineOrder - Wednesday, July 24, 2013 - linkThe only time you can trust anything nVidia says about Tegra and product delivery is when it's been shipping for weeks and owned by consumers. Otherwise, they'll lie to your face right up until the very day they are supposed to be shipping product to consumers and then shrug and say, "Oh, sorry. Yah, not happening. Don't know when exactly it'll ship, but hey, it was totally unexpected. We totally didn't know we were going to miss the date until... just now."
This is why they lost so many contracts to Qualcomm, including the Nexus one. They're just way too unreliable.
Having such great API support and having it be highly compatible with PC gaming and console gaming will only be great when it happens to a company that actually delivers product on time and within promised spec.
And that company will almost certainly be Qualcomm.
Krysto - Wednesday, July 24, 2013 - linkNot denying what you said, but today I realized they probably dropped Tegra because Qualcomm supports OpenGL ES 3.0, and it was one of the main features of Android 4.3. Tegra 4 doesn't support it.
lmcd - Wednesday, July 24, 2013 - linkThat has to be why, in my opinion.
HighTech4US - Wednesday, July 24, 2013 - linkHaters gotta Hate.
lmcd - Wednesday, July 24, 2013 - linkNot like Qualcomm dropped the ball on Windows drivers or anything...
Of course it turned out that market was worthless but you should pay a little more attention!