From WikiChip
Editing intel/microarchitectures/ice lake (client)
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 55: | Line 55: | ||
|l1d desc=12-way set associative | |l1d desc=12-way set associative | ||
|l2=512 KiB | |l2=512 KiB | ||
− | |l2 per= | + | |l2 per=512 KiB |
− | |l2 desc= | + | |l2 desc=12-way set associative |
|l3=2 MiB | |l3=2 MiB | ||
|l3 per=core | |l3 per=core | ||
Line 86: | Line 86: | ||
| <s>{{intel|Ice Lake S|l=core}}</s>? || <s>ICL-S</s> || <s>Performance-optimized lifestyle</s> || || <s>Desktop performance to value, AiOs, and minis</s> | | <s>{{intel|Ice Lake S|l=core}}</s>? || <s>ICL-S</s> || <s>Performance-optimized lifestyle</s> || || <s>Desktop performance to value, AiOs, and minis</s> | ||
|} | |} | ||
− | |||
− | |||
− | |||
== Process Technology== | == Process Technology== | ||
− | {{ | + | {{see also|intel/microarchitectures/cannon lake#Process_Technology|l1=Cannon Lake § Process Technology}} |
− | + | Ice Lake is fabricated on Intel's second-generation enhanced [[10 nm process]] called "10 nm+". Versus the first generation 10nm which was used for {{\\|Cannon Lake}}, 10nm+ features higher performance through higher drive current for the same power envelope. Intel says that Ice Lake is built on their learnings from their Cannon Lake products which were largely treated as a learning vehicle. Between Cannon Lake and Ice Lake, a number of changes were made in order to improve the process for their products. One such change was the addition of an extra metal layer (originally said to be 12, is now presumably 13 on Ice Lake) in order to improve the power delivery of the chip. Additionally, they have improved the threshold voltage of the transistors as well as their MIM cap among other changes. | |
− | + | [[File:intels 10+ and 10++.png|750px]] | |
{{clear}} | {{clear}} | ||
Line 239: | Line 236: | ||
− | Previously (e.g., with {{\\|Whiskey Lake}}), for OEMs to support Thunderbolt 3 in mobile devices, they had to use Intel's Titan Ridge controller. Titan Ridge was a discrete Thunderbolt 3 chip that came with either one or two dedicated [[Thunderbolt 3]] ports. In order to support everything that was necessary (e.g., legacy [[USB 2]] as well as high speed PCIe Gen 3), the controller was connected to both the CPU and the | + | Previously (e.g., with {{\\|Whiskey Lake}}), for OEMs to support Thunderbolt 3 in mobile devices, they had to use Intel's Titan Ridge controller. Titan Ridge was a discrete Thunderbolt 3 chip that came with either one or two dedicated [[Thunderbolt 3]] ports. In order to support everything that was necessary (e.g., legacy [[USB 2]] as well as high speed PCIe Gen 3), the controller was connected to both the CPU and the hipset. The chipset was connected over four PCIe Gen 3 lanes. The CPU had two DisplayPort connections. Each of those passed over four PCIe Gen 3 lanes. In order to offer legacy I/O support, a direct USB 2.0 link from the PCH went to the port. For charging capabilities, the port was also connected directly to a Power Deliver (PD) controller. In total, 17 PCIe Gen 3 lanes operating at around 8 GT/s were required between the Titan Ridge controller and the chipset and CPU. |
Due to the design complexity introduced by the discrete controller, most mobile devices that made use of Titan Ridge only supported it on one side of the device - typically on the side of the device closer to the controller itself. | Due to the design complexity introduced by the discrete controller, most mobile devices that made use of Titan Ridge only supported it on one side of the device - typically on the side of the device closer to the controller itself. |
Facts about "Ice Lake (client) - Microarchitectures - Intel"
codename | Ice Lake (client) + |
core count | 2 + and 4 + |
designer | Intel + |
first launched | May 27, 2019 + |
full page name | intel/microarchitectures/ice lake (client) + |
instance of | microarchitecture + |
instruction set architecture | x86-64 + |
manufacturer | Intel + |
microarchitecture type | CPU + |
name | Ice Lake (client) + |
pipeline stages (max) | 19 + |
pipeline stages (min) | 14 + |
process | 10 nm (0.01 μm, 1.0e-5 mm) + |