ashFTW
Senior member
- Sep 21, 2020
- 325
- 247
- 126
Maybe future Gaudi and FPGA tiles can be brought into this framework as well.Speculation: Falcon Ridge built on the same platform as Granite and Sierra Rapids, continuing the path to Zettascale.
View attachment 62607
I'm repeating myself a lot, but perhaps this helps...
We can break this discussion down to two questions. Let's answer the first one, and then answering the second becomes much easier.
Of course you're skeptical, as would be any rational person. "Extraordinary claims require extraordinary evidence" and certainly I haven't presented any. So just take it on faith for now that I believe Royal is capable of even more than rumored, insane as that may sound. There will be plenty of time for I-told-you-sos later, haha.Yea I'm not sure if I buy the fantastic, 30%+ gains even for the Royal Cove project. We'll see when it happens. Yes I can believe amazing amount of effort and reorganization of teams would happen, but in terms of absolute numbers I am skeptical.
Think the original members largely came from Intel Labs, along with one or two high profile hires. Actually, success for Royal might very well kill Core, so that'll be interesting to watch play out. Might even coexist for a time.
Ok, something's been bugging me since the announcement the other day, and I finally figured out what it is. They've changed the graphic!Speculation: Falcon Ridge built on the same platform as Granite and Sierra Rapids, continuing the path to Zettascale.
View attachment 62607
The switch was probably made towards the end of ‘21 after Pat joined Intel. A more competitive product was needed (including a more advanced process) to counter AMD, Nvidia, and ARM advance. This gave them 3 years to ‘24. That pace is urgent, but perhaps not “break-neck” crazy.a) Granite Rapids itself changed topologies when they delayed it to '24. Possible, but that seems like a huge risk.
This looks more like a “2 stack” design, similar to Ponte Vecchio. Maybe they switched to “4 stack” design once they realized they needed to push the release by a year and move to Intel 3 to compete better, while also better aligning with the evolving Falcon Shores design. Smaller reticle size with High NA EUV use will also start to play out soon.Which looks vaguely similar to what they've shown for Granite Rapids:
![]()
But now they've shown this, which looks like nothing else they've shown before.
It could be ‘25. Parts of Falcon Shores are very likely to be on Intel 20A, especially the Xe parts. The x86 parts can be GNR or SRR on Intel 3. Now that the designs are disaggregated, the various tiles can progress independently and still come together in yearly updates, as long as the interfaces are preserved.b) What they're showing here is actually a sneak peak at a post-GNR topology, and Falcon Shores is more like '25 or '26.
Sapphire Rapids with and without HBM use the same Eagle Stream platform/socket, don’t they? HBM concerns should be internal to the socket. Do all XCC Sapphire Rapids tiles not have the ability to interface with HBM2e?I have doubts on Falcon Shores using the same platform as Granite Rapids. Maybe Granite Rapids HBM?
I see it as a spiritual successor to the -AP line, and further back, the socketed Xeon Phi.
Ok, I see that they have different size packages, but aren’t they both using LGA 4677, and the Eagle Stream PCH?@ashFTW Sapphire Rapids with HBM clearly uses a different package. And it's much larger too.
Thanks!GPIO stands for "General Purpose I/O". Systems have tons of I/O buses and not all are fancy like UPI or DMI. GP in the GPIO means that it can be reconfigured for what's needed. But of course much less bandwidth.
Imagine a intel console with 16 or 24 e-cores.. sony and Microsoft better call intel for the ps6 or xbox 😁Yea and 8+32 would take way less space and power. 8+32 = 16
8+64 equals 24P. Now tell me how that performs!
And there's an additional benefit where the P core can be P+, and be bigger and more performant than otherwise for even better ST performance and responsiveness. That's the whole point of hybrid. You get to specialize the cores way more than otherwise.
The real promise is this: Rather than doing 8+64 in place of 24P, you do 8 supercharged P cores + 32 E cores. Of course the P cores would be a lot larger. Let's say 30% faster per clock and twice the size.
Remember, this is in addition to whatever they would do normally. So I believe for risk mitigation it'll be spread out over few generations. So rather than new gen P being 18% faster, you have it being 24% faster for next 4-5 generations. And at the end, you have a very large P core and sea of E cores. Supercharging it for low and high thread.
Imagine a intel console with 16 or 24 e-cores.. sony and Microsoft better call intel for the ps6 or xbox 😁
Maybe intel wants to score 4.500 or 5000 single core performance on cimebench with royal core or panther coveIn the reddit leak "the biggest architectural change in CPU architecture since the Core architecture" was claimed for Nova Lake. There are rumors about Panther Lake after Lunar, I hope it doesn't mean it has been delayed one generation. If there is Panther Lake the Panther Cove core naming would make sense though.
Intel's (stylistic) block diagram from HotChips doesn't show any significant space for EMIB. The whole point of EMIB is that it is a small piece of silicon embedded in the package; it is not part of the main die itself. Those are 10 separate tiles.Speculation: Emerald Rapids tile (~480 mm2) with an additional row of cores. Or, up to 76 cores for the chip.
View attachment 62601
Intel has had low margin businesses before: modem, NAND. (Gross margin wasn't why Intel exited those businesses.)Intel historically wants margins too high for them to show any interest in consoles.
Intel has had low margin businesses before: modem, NAND. (Gross margin wasn't why Intel exited those businesses.)
I don't think consoles need that many E-cores.Imagine a intel console with 16 or 24 e-cores.. sony and Microsoft better call intel for the ps6 or xbox 😁
So I initially thought that like Meteor Lake, maybe one is for representative purposes only. Seems totally possible. But then why change it? So I've got two alternative theories.
a) Granite Rapids itself changed topologies when they delayed it to '24. Possible, but that seems like a huge risk.
b) What they're showing here is actually a sneak peak at a post-GNR topology, and Falcon Shores is more like '25 or '26.
Yea and 8+32 would take way less space and power. 8+32 = 16
8+64 equals 24P. Now tell me how that performs!