1. Multi-core systems System Architecture COMP25212 Daniel Goodman Advanced Processor Technologies Group

2. Multi-Cores are Coming (here?)  Many processors in normal desktops/laptops are ‘dual core’ or ‘quad core’ What does this mean? Why is it happening? How are they different? Where are they going? Do they change anything?

3. Moore’s Law 45nm Fun Facts  A human hair= 90000nm  Bacteria = 2000nm  Silicon atom = 0.24nm

4. The need for Multi-Core  For over 30 years the performance of processors has doubled every 2 years  Driven mainly by shrinkage of circuits  Smaller circuits more transistors per chip shorter connections lower capacitance  Smaller circuits go faster  In early 2000s the rate started to decrease

5. Motivation

6. Is cooling a problem? Intel Nehalem: In the event of all the cores not being used, the unused cores can be shutdown allowing the remaining cores to use the spare resources and speed up.

7. The Memory Wall  Processor utilization (15%-25%) Memory Speed is failing to keep up with processor speed. Why?

8. The End of “Good Times”  Slowdown for several reasons Power density increasing (more watts per unit area) - cooling is a serious problem Small transistors have less predictable characteristics Architectural innovation hitting design complexity problems (limited ILP) Memory does not get faster at the same rate as processors

9. A solution is replication  Put multiple CPUs (cores) on a single integrated circuit (chip)  Use them in parallel to achieve higher performance  Simpler to design than a more complex single processor  Need more computing power – just add more cores?

10. How to Connect Them?  Could have independent processor/store pairs with interconnection network  At the software level the majority of opinion is that shared memory is the right answer for a general purpose processor  But, when we consider more than a few cores, shared memory becomes more difficult to implement

11. Can We Use Multiple Cores?  Small numbers of cores can be used for separate tasks – e.g. run a virus checker on one core and Word on another  If we want increased performance on a single application we need to move to parallel programming  General purpose parallel programming is known to be hard – consensus is that new approaches are needed

12. There Are Problems  We don’t know how to engineer extensible memory systems  We don’t know how to write general purpose parallel programs  If we develop new approaches to parallel programming do they fit with existing serial processor designs?

13. Intel Core i7 (Nehalem) 2 Simultaneous Multi-Threading per core

14. Front Side Bus Traditional Structure – "Historical View” (Processor, Front Side Bus, North Bridge, South Bridge) Main Memory (DRAM) Processor and Cache (single die/chip SRAM) North Bridge Chip Memory Controller Graphics Card Motherboard South Bridge Chip I/O Buses (PCIe, USB, Ethernet, SATA HD) …

15. QPI or HT Typical Multi-core Structure Main Memory (DRAM) Input/Output Hub Graphics Card Motherboard Input/Output Controller I/O Buses (PCIe, USB, Ethernet, SATA HD) … PCIe On Chip core L1 Inst L1 Data Memory Controller core L1 Inst L1 Data L2 Cache L3 Shared Cache

16. Simplified Multi-Core Structure core L1 Inst Data core L1 Inst Data core L1 Inst Data core L1 Inst Data Level 2 Cache Main Memory On Chip Shared Bus

17. Nehalem Caches  Private L1: split D$ & I$, 32KB each, 4-way I$ & 8-way set associative, approx. LRU, block size 64 bytes, write-back & write-allocate  Private L2: 8-way set associative, idem.  Shared L3: 16-way set associative, idem

18. Cache Coherence?

19. Summary  Multi-core systems are here to stay Physical limitations Design costs  The industry did not want to come but there is no current alternative  One of the biggest changes for our field General Purpose Parallel Programming must be made tractable  For further reading Patterson and Hennessy 4 th Edition Chapter 1