From WikiChip
Editing intel/microarchitectures/cascade lake

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

This page supports semantic in-text annotations (e.g. "[[Is specified as::World Heritage Site]]") to build structured and queryable content provided by Semantic MediaWiki. For a comprehensive description on how to use annotations or the #ask parser function, please have a look at the getting started, in-text annotation, or inline queries help pages.

Latest revision Your text
Line 401: Line 401:
 
[[File:cascade-lake-optane-dimm-encryption.png|right|thumb|PMM Encryption]]
 
[[File:cascade-lake-optane-dimm-encryption.png|right|thumb|PMM Encryption]]
 
One of the unique problems associated with persistent memory is the security of the persistent data itself. To that end, Optane DIMMs protects all data with 256b AES-XTP. There are two supported modes. The first one is memory mode where the DIMM is treated like DRAM memory (one big cache) and as such, the key is regenerated each boot and data is lost on a power cycle. The second mode is App Direct which keeps the key on a power cycle. In this mode, the passphrase must be securely stored to unlock the data. Interestingly, one of the features that are currently missing is support for any form of virtualization. Currently, in a virtualized environment, the DIMM is unlocked using a single passphrase meaning the host has access to all the data. It’s reasonable to expect that in future Xeons, support for virtualization will be added such that data can be remained encrypted and private for that VM.
 
One of the unique problems associated with persistent memory is the security of the persistent data itself. To that end, Optane DIMMs protects all data with 256b AES-XTP. There are two supported modes. The first one is memory mode where the DIMM is treated like DRAM memory (one big cache) and as such, the key is regenerated each boot and data is lost on a power cycle. The second mode is App Direct which keeps the key on a power cycle. In this mode, the passphrase must be securely stored to unlock the data. Interestingly, one of the features that are currently missing is support for any form of virtualization. Currently, in a virtualized environment, the DIMM is unlocked using a single passphrase meaning the host has access to all the data. It’s reasonable to expect that in future Xeons, support for virtualization will be added such that data can be remained encrypted and private for that VM.
 
== Scalability ==
 
{{see also|intel/ultra path interconnect|l1=Ultra Path Interconnect}}
 
Cascade Lake continues to use {{intel|Ultra Path Interconnect}} (UPI) which was {{\\|Skylake (server)#Scalability|first introduced}} with {{\\|Skylake (server)|Skylake}}. UPI is a high-efficiency coherent interconnect for scalable systems, allowing multiple processors to share a single shared address space. Depending on the exact model, each processor can have either two or three UPI links connecting to the other processors.
 
 
Depending on the exact model, Cascade Lake processors can scale from 2-way all the way up to 8-way multiprocessing. Note that the high-end models that support 8-way multiprocessing also only come with three UPI links for this purpose while the lower end processors can have either two or three UPI links. Below are the typical configurations for those processors.
 
 
 
<div style="display: inline-block;">
 
<div style="float: left; margin: 15px; text-align: center;">'''2-way SMP; 2 UPI links'''<br><br>[[File:cascade lake sp 2-way 2 upi.svg|400px]]</div>
 
<div style="float: left; margin: 15px; text-align: center;">'''2-way SMP; 3 UPI links'''<br><br>[[File:cascade lake sp 2-way 3 upi.svg|400px]]</div>
 
</div>
 
 
 
<div style="display: inline-block;">
 
<div style="float: left; margin: 15px; text-align: center;">'''4-way SMP; 2 UPI links'''<br><br>[[File:cascade lake sp 4-way 2 upi.svg|400px]]</div>
 
<div style="float: left; margin: 15px; text-align: center;">'''4-way SMP; 3 UPI links'''<br><br>[[File:cascade lake sp 4-way 3 upi.svg|400px]]</div>
 
</div>
 
 
 
<div style="display: inline-block;">
 
<div style="text-align: center;">'''8-way SMP; 3 UPI links'''<br><br>[[File:cascade lake sp 8-way 3 upi.svg|400px]]</div>
 
</div>
 
  
 
== All Cascade Lake Chips ==
 
== All Cascade Lake Chips ==

Please note that all contributions to WikiChip may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see WikiChip:Copyrights for details). Do not submit copyrighted work without permission!

Cancel | Editing help (opens in new window)
codenameCascade Lake +
core count2 +, 4 +, 6 +, 8 +, 10 +, 12 +, 16 +, 18 +, 20 +, 22 +, 24 +, 26 +, 28 +, 32 +, 48 + and 56 +
designerIntel +
first launched2019 +
full page nameintel/microarchitectures/cascade lake +
instance ofmicroarchitecture +
instruction set architecturex86-64 +
manufacturerIntel +
microarchitecture typeCPU +
nameCascade Lake +
pipeline stages (max)19 +
pipeline stages (min)14 +
process14 nm (0.014 μm, 1.4e-5 mm) +