• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

64 core EPYC Rome (Zen2)Architecture Overview?

Page 34 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Looks like the original leak was not totally baseless.
The OP perhaps but the Thread Starter also believed that AMD would have not used 3 chiplets for Ryzen 3000

Think about it: if there are 8 CPU dies, then each one must be 8C/16T with 1 DDR4 memory channel. Such a die is unsuitable for Ryzen. You could use 2 CPU dies + 1 I/O die to make a 16C/32T + 2ch DDR4 MCM package for Ryzen desktop but I don't think it makes sense. Besides, AM4 is a small PGA package, I doubt you can fit a 3-die MCM on it.
 
Not sure how many people here care about SEV, Secure Encrypted Virtualization. (Personally I think it's a killer feature which I agree with Norrod should be considered standard soon.)

Anyway Forrest Norrod stated the following aside in an interview:
"The virtual machine is encrypted. So the virtual machine or container or even a process—actually the way that we've implemented it you can make it any one of those three—and it's independent. It's managed by a separate key manager in our security processor. So the systems administrator for the server does not control that key. The user of that VM running their workloads on Amazon [Web Services] can control that key, so all of their VMs work as normal, work full performance, there's no performance impact, but even if Amazon wanted to, they couldn't look into that virtual machine."

I didn't know this essentially works on a process level. This is great as this should allow to encrypt/isolate any process even without using VMs or containers.
Another neat tidbit:
SEV originates from the semi custom business work on Xbox One and Playstation 4.
https://www.crn.com/news/components...on-work-led-to-a-big-security-feature-in-epyc
 
these new slides are totally worth looking at


see if you just made that bit thats like 1/25th of the core 6 units instead of 4 you would get 50% more IPC!!!

The cost for chiplet vs monolithic also confirms what we all knew 🙂
 
Back
Top