Microprocessor functions outside of, but closely connected to, the core
This article needs to be updated. Please help update this article to reflect recent events or newly available information.(January 2017)
"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.[1] It has been called "system agent" since the release of the Sandy Bridgemicroarchitecture.[2]
Specifically, the microarchitecture of the Nehalem-EX uncore is broken down into a number of modular units. The main uncore interface to the core is the so-called cache box (CBox), which interfaces with the last level cache (LLC) and is responsible for managing cache coherency. Multiple internal and external QPI links are managed by physical-layer units, referred to as PBox. Connections between the PBox, CBox, and one or more iMCs (MBox) are managed by the system configuration controller (UBox) and a router (RBox).[6]
Removal of serial bus controllers from the Intel uncore further enables increased performance by allowing the uncore clock (UCLK) to run at a base of 2.66GHz, with overclocking limits in excess of 3.44GHz.[7] This increased clock rate allows the core to access critical functions (such as the IMC) with significantly less latency, typically reducing core access times to DRAM by 10ns or more.
"Thunderbolt™ Technology for Developers." Intel.com. Retrieved March 30, 2025.
Anand Lal Shimpi, "Intel's Sandy Bridge Architecture Exposed," AnandTech, September 14, 2010; updated information available in later reviews of later architectures.
"Intel® Xeon® Processor Uncore Programming Guide." Intel.com. Retrieved March 2025.