• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Sandy Bridge block diagram

qubit

Overclocked quantum bit
Joined
Dec 6, 2007
Messages
17,865 (2.85/day)
Location
Quantum Well UK
System Name Quantumville™
Processor Intel Core i7-2700K @ 4GHz
Motherboard Asus P8Z68-V PRO/GEN3
Cooling Noctua NH-D14
Memory 16GB (2 x 8GB Corsair Vengeance Black DDR3 PC3-12800 C9 1600MHz)
Video Card(s) MSI RTX 2080 SUPER Gaming X Trio
Storage Samsung 850 Pro 256GB | WD Black 4TB | WD Blue 6TB
Display(s) ASUS ROG Strix XG27UQR (4K, 144Hz, G-SYNC compatible) | Asus MG28UQ (4K, 60Hz, FreeSync compatible)
Case Cooler Master HAF 922
Audio Device(s) Creative Sound Blaster X-Fi Fatal1ty PCIe
Power Supply Corsair AX1600i
Mouse Microsoft Intellimouse Pro - Black Shadow
Keyboard Yes
Software Windows 10 Pro 64-bit
I'm trying to find a block diagram for Sandy Bridge, but I can't find one. In particular, I want one that shows how they've implemented the various bits in each core. I'm curious if it has a full FPU per core and if it supports Hyper Threading. I'd also be on the lookout for anything else interesting in this diagram.

I don't need this for any special reason other than geeky curiousity (which I'm sure all my friends on here will totally relate to :D) since I have a Sandy 2700K.

And before anyone tells me to jfgi, I've already done some frantic googling, including limiting it to intel.com but come up with nothing useful. :ohwell:
 

Norton

Moderator - Returning from the Darkness
Joined
Dec 21, 2011
Messages
14,108 (2.95/day)
Location
Northeast USA
System Name Main PC- Gamer- Main Cruncher/Folder and too many crunching/folding rigs
Processor Ryzen 5900X- Ryzen 5950X- Ryzen 3950X and etc...
Motherboard Asrock X570 Extreme4- MSI X570S Tomahawk MAX WiFi- MSI B450M Bazooka Max and etc...
Cooling Noctua NH-U14S (dual fan)- EK 360 AIO with push/pull fans- Corsair H115i RGB Pro XT and etc...
Memory 2x16GB GSkill FlareX 3200/c14- 4x8GB Corsair Vengeance 3600/c16- 2x16GB Team 3600/c18 and etc..
Video Card(s) MSI Gaming RX 6800- Asus RTX 3070 TUF OC- MSI Ventus GTX 1660Ti and etc...
Storage Main PC (1TB WD SN850- 2TB PNY CS 3040- 2TB Seagate Firecuda) and etc...
Display(s) Main PC (2x24" Dell UltraSharp U2414H)
Case Phanteks P600s- Seasonic Q704- Fractal Meshify C and etc...
Audio Device(s) Logitech Z625 THX 2.1 speakers
Power Supply EVGA 750 G3- SeaSonic DGC 750- EVGA P2 850 and etc...
Mouse G300s
Keyboard Corsair K65
VR HMD N/A
Software Windows 10 Pro or Ubuntu
Benchmark Scores Why sit on the Bench when you can get in the game and Crunch!!!

Aquinus

Resident Wat-man
Joined
Jan 28, 2012
Messages
13,173 (2.77/day)
Location
Concord, NH, USA
System Name Apollo
Processor Intel Core i9 9880H
Motherboard Some proprietary Apple thing.
Memory 64GB DDR4-2667
Video Card(s) AMD Radeon Pro 5600M, 8GB HBM2
Storage 1TB Apple NVMe, 4TB External
Display(s) Laptop @ 3072x1920 + 2x LG 5k Ultrafine TB3 displays
Case MacBook Pro (16", 2019)
Audio Device(s) AirPods Pro, Sennheiser HD 380s w/ FIIO Alpen 2, or Logitech 2.1 Speakers
Power Supply 96w Power Adapter
Mouse Logitech MX Master 3
Keyboard Logitech G915, GL Clicky
Software MacOS 12.1
Intel's execution pipeline hasn't changed a whole lot from the C2D, since the memory controller has moved to the CPU on Nehelem, it's safe to assume anything used on skt1366, 1156, 1155, and 2011 is going to be about the same. Intel isn't going to release anything too specific about their cores and what they do to make them go fast, but you may be looking for something like this.

This is a bit out of the pipeline for nehelem, it really hasn't change too much but maybe you can find something on SB, but it shouldn't be too far off.

nehelem_pipeline.JPG


Edit: Aha, I think you want this: http://www.intel.com/content/dam/doc/manual/64-ia-32-architectures-optimization-manual.pdf

I think this might be what you wanted:
sb_pipeline.JPG


I've actually never taken the time to look at this. Makes a lot of sense why Intel can run single threads really quickly. There isn't much for shared components, each instruction must execute pretty quickly.
 
Last edited:
Top