Lesson plan

Uncore

"Uncore" is a term used by Intel to describe the functions of a microprocessor that are not in the core, but which must be closely connected to the core to achieve high performance. It was introduced with the Nehalem microarchitecture. It has been called "system agent" since the release of the Sandy Bridge microarchitecture. The Uncore/SA handles the functionalities traditionally assigned to the northbridge: QPI controllers, L3 cache, snoop agent pipeline, on-die memory controller, on-die PCI Express Root Complex, and Thunderbolt controller. Integration of these functions into the core makes them physically closer, thereby reducing their access latency. In contrast, the "core" (processor) component consists of the control unit, ALU, FPU, and L1 and L2 caches. Other bus controllers such as SPI and LPC are part of the chipset (Platform Controller Hub), the equivalent of the southbridge. Further integration has since eliminated the PCH from the motherboard for a system-in-package design on mobile SKUs.

Back to article

Article summary

"Uncore" is a term used by Intel to describe the functions of a microprocessor that are not in the core, but which must be closely connected to the core to achieve high performance. It was introduced with the Nehalem microarchitecture. It has been called "system agent" since the release of the Sandy Bridge microarchitecture. The Uncore/SA handles the functionalities traditionally assigned to the northbridge: QPI controllers, L3 cache, snoop agent pipeline, on-die memory controller, on-die PCI Express Root Complex, and Thunderbolt controller. Integration of these functions into the core makes them physically closer, thereby reducing their access latency. In contrast, the "core" (processor) component consists of the control unit, ALU, FPU, and L1 and L2 caches. Other bus controllers such as SPI and LPC are part of the chipset (Platform Controller Hub), the equivalent of the southbridge. Further integration has since eliminated the PCH from the motherboard for a system-in-package design on mobile SKUs.

Key claims

No claims recorded.

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  3. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.