How Game Engines Can Inspire EDA Tools Development: A use case for an open-source physical design library

Transcription

1 How Game Engines Can Inspire EDA Tools Development: A use case for an open-source physical design library Tiago Fontana, Renan Netto, Vinicius Livramento, Chrystian Guth, Sheiny Almeida, Laércio Pilla, José Luís Güntzel Embedded Computing Lab, Computer Science Department Federal University of Santa Catarina, Brazil ISPD - March, Portland, OR phidian

2 Outline 1 Introduction 2 Memory Hierarchy 3 Modularity 4 The Entity-Component System Design Pattern 5 Experimental Results 6 Conclusions

3 Modern Game Engines Process huge amount of data Model realistic physical systems Render high-resolution graphics Run artificial intelligence engines Vinicius Livramento ISPD - March, Portland, OR 3

4 Modern Game Engines Memory: better cache locality Parallelism: multithreading and GPU Modularity: few data dependency Testing: small functions Vinicius Livramento ISPD - March, Portland, OR 4

5 Understanding the Memory Hierarchy Vinicius Livramento ISPD - March, Portland, OR 5

6 How Object-Oriented Design (OOD) Leads to More Cache Misses Vinicius Livramento ISPD - March, Portland, OR 6

7 How Object-Oriented Design (OOD) Leads to More Cache Misses Vinicius Livramento ISPD - March, Portland, OR 6

8 How Data-Oriented Design (DOD) Improves Cache Locality Vinicius Livramento ISPD - March, Portland, OR 7

9 How Data-Oriented Design (DOD) Improves Cache Locality Vinicius Livramento ISPD - March, Portland, OR 7

10 Modularity: Modeling Nets and Pins P1 N1 N3 P4 P6 B P7 N4 P8 P2 N2 P3 A P5 Vinicius Livramento ISPD - March, Portland, OR 8

11 Modularity: Modeling Nets and Pins Using OOD Vinicius Livramento ISPD - March, Portland, OR 9

12 Modularity: Modeling Nets and Pins Using OOD Vinicius Livramento ISPD - March, Portland, OR 9

13 Modularity: Integrating Placement and Timing Using OOD Vinicius Livramento ISPD - March, Portland, OR 10

14 Modularity: Modeling Nets and Pins Using DOD Vinicius Livramento ISPD - March, Portland, OR 11

15 Modularity: Modeling Nets and Pins Using DOD Vinicius Livramento ISPD - March, Portland, OR 11

16 Modularity: Integrating Placement and Timing Using DOD Vinicius Livramento ISPD - March, Portland, OR 12

17 Entities and Components (Properties) Vinicius Livramento ISPD - March, Portland, OR 13

18 The Entity System: find, create, and delete entity in O(1) Vinicius Livramento ISPD - March, Portland, OR 14

19 The Entity System: find, create, and delete entity in O(1) Vinicius Livramento ISPD - March, Portland, OR 14

20 The Entity System: find, create, and delete entity in O(1) Vinicius Livramento ISPD - March, Portland, OR 14

21 Relationships Between Entities: aggregation and composition AGGREGATION Entity System: Nets Net 1 - Name: N1 - Pins: Net 2 - Name: N2 - Pins: Entity System: Pins Pin 1 - Name: P1 - Net: 1 Pin 3 - Name: P3 Pin 5 - Name: P5 - Net: 1 Pin 2 - Name: P2 Pin 4 - Name: P4 - Net: 1 Pin 6 - Name: P6 Vinicius Livramento ISPD - March, Portland, OR 15

22 Relationships Between Entities: aggregation and composition AGGREGATION Entity System: Nets Net 1 - Name: N1 - Pins: Net 2 - Name: N2 - Pins: Entity System: Pins Pin 1 - Name: P1 - Net: 1 Pin 3 - Name: P3 Pin 5 - Name: P5 - Net: 1 Pin 2 - Name: P2 Pin 4 - Name: P4 - Net: 1 Pin 6 - Name: P6 Entity System: Nets Net 2 - Name: N2 - Pins: Entity System: Pins Pin 1 - Name: P1 - Net: -- Pin 3 - Name: P3 Pin 2 - Name: P2 Pin 4 - Name: P4 - Net: -- Pin 5 - Name: P5 - Net: -- Pin 6 - Name: P6 Vinicius Livramento ISPD - March, Portland, OR 15

23 Relationships Between Entities: aggregation and composition Entity System: Nets Net 1 - Name: N1 - Pins: Net 2 - Name: N2 - Pins: AGGREGATION Entity System: Pins Pin 1 - Name: P1 - Net: 1 Pin 3 - Name: P3 Pin 5 - Name: P5 - Net: 1 Pin 2 - Name: P2 Pin 4 - Name: P4 - Net: 1 Pin 6 - Name: P6 Entity System: Cells Cell 1 - Name: C1 - Pins: Cell 2 - Name: C2 - Pins: COMPOSITION Entity System: Pins Pin 1 - Name: P1 - Cell: 1 Pin 3 - Name: P3 - Cell: 2 Pin 5 - Name: P5 - Cell: 1 Pin 2 - Name: P2 - Cell: 2 Pin 4 - Name: P4 - Cell: 1 Pin 6 - Name: P6 - Cell: 2 Entity System: Nets Net 2 - Name: N2 - Pins: Entity System: Pins Pin 1 - Name: P1 - Net: -- Pin 3 - Name: P3 Pin 2 - Name: P2 Pin 4 - Name: P4 - Net: -- Pin 5 - Name: P5 - Net: -- Pin 6 - Name: P6 Vinicius Livramento ISPD - March, Portland, OR 15

24 Relationships Between Entities: aggregation and composition Entity System: Nets Net 1 - Name: N1 - Pins: Net 2 - Name: N2 - Pins: AGGREGATION Entity System: Pins Pin 1 - Name: P1 - Net: 1 Pin 3 - Name: P3 Pin 5 - Name: P5 - Net: 1 Pin 2 - Name: P2 Pin 4 - Name: P4 - Net: 1 Pin 6 - Name: P6 Entity System: Cells Cell 1 - Name: C1 - Pins: Cell 2 - Name: C2 - Pins: COMPOSITION Entity System: Pins Pin 1 - Name: P1 - Cell: 1 Pin 3 - Name: P3 - Cell: 2 Pin 5 - Name: P5 - Cell: 1 Pin 2 - Name: P2 - Cell: 2 Pin 4 - Name: P4 - Cell: 1 Pin 6 - Name: P6 - Cell: 2 Entity System: Nets Entity System: Pins Entity System: Cells Entity System: Pins Net 2 - Name: N2 - Pins: Pin 1 - Name: P1 - Net: -- Pin 3 - Name: P3 Pin 2 - Name: P2 Pin 4 - Name: P4 - Net: -- Cell 2 - Name: C2 - Pins: Pin 2 - Name: P2 - Cell: 2 Pin 6 - Name: P6 - Cell: 2 Pin 3 - Name: P3 - Cell: 2 Pin 5 - Name: P5 - Net: -- Pin 6 - Name: P6 Vinicius Livramento ISPD - March, Portland, OR 15

25 Infrastructure & Experimental Results ICCAD 2015 infrastructure: 8 circuits with sizes between 768k and 1.93M cells Objective: Analyze cache misses and runtime Scenario A: check if all circuit cells positions lie within the circuit s boundaries Scenario B: computing the interconnection wirelength for all circuit nets Machine (31GB) Processor Cache L3 (6144KB) L2 (256KB) L2 (256KB) L2 (256KB) L2 (256KB) L1d (32KB) L1d (32KB) L1d (32KB) L1d (32KB) L1i (32KB) L1i (32KB) L1i (32KB) L1i (32KB) Processor Elements Core P#0 Core P#1 Core P#2 Core P#3 PU P#0 PU P#1 PU P#2 PU P#3 Vinicius Livramento ISPD - March, Portland, OR 16

26 Total Cache Miss for Scenario A: exploiting cache locality Vinicius Livramento ISPD - March, Portland, OR 17

27 Total Cache Miss for Scenario A: exploiting cache locality Vinicius Livramento ISPD - March, Portland, OR 17

28 Runtime for Scenario A: exploiting cache locality Vinicius Livramento ISPD - March, Portland, OR 18

29 Runtime for Scenario A: exploiting cache locality Vinicius Livramento ISPD - March, Portland, OR 18

30 Total Cache Miss for Scenario B: less benefits from cache locality Vinicius Livramento ISPD - March, Portland, OR 19

31 Total Cache Miss for Scenario B: less benefits from cache locality Vinicius Livramento ISPD - March, Portland, OR 19

32 Conclusions and Perspectives Data-Oriented design can be efficiently applied to physical design Modular code is more suitable for parallel implementations Better testability Opportunities for future work Organize data according to access pattern Multiple copies of the same vector of properties sorted in different order Vinicius Livramento ISPD - March, Portland, OR 20

33 How Game Engines Can Inspire EDA Tools Development: A use case for an open-source physical design library Questions? Vinicius Livramento vinilivramento@gmail.com phidian

34 Aggregation code example class Net : public entity_system::entitybase{ }; class Pin : public entity_system::entitybase{ }; EntitySystem<Net> nets; EntitySystem<Pin> pins; Aggregation<Net, Pin> aggregation(nets, pins); Cell n3 = nets.add(); Pin p5 = pins.add(); Pin p6 = pins.add(); P1 P2 N2 P3 N1 A P5 N3 P4 P6 B P7 N4 P8 aggregation.addassociation(n3, p5); aggregation.addassociation(n3, p6); Vinicius Livramento ISPD - March, Portland, OR 22

35 Composition code example class Cell : public entity_system::entitybase{ }; class Pin : public entity_system::entitybase{ }; EntitySystem<Cell> cells; EntitySystem<Pin> pins; Composition<Cell, Pin> composition(cells, pins); Cell a = cells.add(); Pin p3 = pins.add(); Pin p5 = pins.add(); P1 P2 N2 P3 N1 A P5 N3 P4 P6 B P7 N4 P8 composition.addassociation(a, p3); composition.addassociation(a, p5); Vinicius Livramento ISPD - March, Portland, OR 23