Garnet2.0: A Detailed On-Chip Network Model Inside a Full-System Simulator

Transcription

1 Garnet2.0: A Detailed On-Chip Network Model Inside a Fll-System Simlator Tshar Krishna gem5 workshop ARM Research Smmit September 11, 2017 Assistant Professor School of ECE and CS Georgia Institte of Technology tshar@ece.gatech.ed

2 Overview What are Networks-On-Chip (NoCs)? Why model NoCs accrately Garnet2.0 Configration Topology Roting Flow-Control Roter Microarchitectre System Integration Network Interface Network Parameters Rnning Garnet with Rby Rby Garnet Standalone Otpt Stats Extensions and FAQs 2

3 Overview What are Networks-On-Chip (NoCs)? Why model NoCs accrately Garnet2.0 Configration Topology Roting Flow-Control Roter Microarchitectre System Integration Network Interface Network Parameters Rnning Garnet with Rby Rby Garnet Standalone Otpt Stats Extensions and FAQs 3

4 Networks-on-Chip 4

5 Introdction to NoCs Core + L1$ Core + L1$ Core + L1$ Core + L1$ A Core + L1$ Core + L1$ LD (A) R1 Req Rsp On-Chip Network Fwd L2$ L2$ L2$ L2$ L2$ L2$ 5

6 Modern NoCs Core L1 D$ L2$ L1 I$ Network Interface L3$/Directory Roter Network Interface converts cache messages (ctrl or data) into packets. Packets get broken down into one or more flits depending on NoC link width Tile 6

7 Network Architectre Topology Roting Flow Control Roter Microarchitectre 7

8 Topology: How to connect nodes with links ~Road Network 8

9 Roting: Which path shold a message take ~Series of road segments from sorce to destination 9

10 Flow Control: When does a message stop/proceed ~Traffic Signals / Stop signs at end of each road segment 10

11 Roter Microarchitectre: How to bild the roters ~Design of traffic intersection (nmber of lanes, algorithm for trning red/green) 11

12 Overview What are Networks-On-Chip (NoCs)? Why model NoCs accrately Garnet2.0 Configration Topology Roting Flow-Control Roter Microarchitectre System Integration Network Interface Network Parameters Rnning Garnet with Rby Rby Garnet Standalone Otpt Stats Extensions and FAQs 12

13 Why model NoCs accrately? Case Stdy I: Directory vs. Broadcast Protocols Case Stdy II: Private vs. Shared L2 1.6 Fll-state Directory HyperTransport Token Coherence 1.2 Shared L2 Private L2 Normalized Rntime Baseline NoC (Intel SCC) FANOUT + FANIN NoC (Krishna et al, MICRO 2011) SMART NoC (Krishna et al, HPCA 2013) 64-core CMP with different NoC Microarchitectres Normalized Rntime Baseline NoC (Intel SCC) SMART NoC (Krishna et al, HPCA 2013) 64-core CMP with different NoC Microarchitectres Different NoC Microarchitectres may lead to different microarchitectral decisions and new design optimization opportnities 64-core CMP rnning PARSEC workloads in fll-system gem5. Average rntime plotted. 13

14 Overview What are Networks-On-Chip (NoCs)? Why model NoCs accrately Garnet2.0 Configration Topology Roting Flow-Control Roter Microarchitectre System Integration Network Interface Network Parameters Rnning Garnet with Rby Rby Garnet Standalone Otpt Stats Extensions and FAQs 14

15 Garnet2.0 Detailed NoC Model Crrently part of Rby Memory System in gem5 Original version (5-stage pipeline) released in 2009 Developed by Niket Agarwal (crrently at Google) and myself New version (1-stage pipeline, more configrability) released in 2016 Resorces Sorce: src/mem/rby/network/garnet2.0 gem5 wiki page: Dev patches + practice labs: 15

16 Topology Each topology is a python file in configs/topologies/ Core + L1$ L2$ DMA Dir ExtLink (bi-directional) R R IntLink (ni-directional) Core + L1$ R R Dir Core + L1$ L2$ L2$ R R Step 1: Instantiate roters and connect to controllers via Ext Links Step 2: Instantiate Int Links and connect to roters in desired topology This is an example of MeshDirCorners_XY.py L2$ L2$ L2$ Core + L1$ Dir Core + L1$ Dir Core + L1$ 16

17 Topology Configrable Parameters Roter roter_latency (in cycles) Can be set per roter Defined in src/mem/rby/network/basicroter.py Link link_latency (in cycles) Can be set per link Defined in src/mem/rby/network/basiclink.py weight (i.e., link weight) To bias roting algorithm [later slides] src_otport (string) and dst_inport (string) Port direction (e.g., East ) Helps with readability of Config file + Adaptive roting algorithms bw_mltiplier (vale) Used by Rby s simple network model, NOT by Garnet Link bandwidth is set inside Garnet via the ni_flit_size parameter [later slides] 17

18 Defalt Topologies Spported Pt2Pt Crossbar Mesh Mesh_XY Mesh_westfirst MeshDirCorners_XY Clster 18

19 Roting Roting table Atomatically poplated based on topology All messages se shortest path In case of mltiple options, the path with the smaller weight is chosen Deterministic Roting Cstom Users can leverage otport/inport direction names associated with each port to implement cstom algorithms (say adaptive) 19

20 Deadlock Avoidance Deadlock: A condition in which a set of agents wait indefinitely trying to acqire a set of resorces D 0 1 x A C 3 w 2 v B Packet A holds bffer (in 1) and wants bffer v (in 2) Packet B holds bffer v (in 2) and wants bffer w (in 3) Packet C holds bffer w (in 3) and wants bffer x (in 0) Packet D holds bffer x (in 0) and wants bffer (in 1) 20

21 Deadlock-free Roting Algorithms Deadlocks may occr if the trns taken form a cycle Removing some trns can make the roting algorithm deadlock free XY Model West-First Trn Model 21

22 Deadlock-free Roting Algorithms Assign weights to bias which links sed first (to ensre no cyclic dependence) XY Roting: Always go X first, then Y DC DA DB SA SB SC Mesh_XY 22

23 Deadlock-free Roting Algorithms Assign weights to bias which links sed first (to ensre no cyclic dependence) West-first Roting: Go W first, then N/S DC DA DB SA SB SC Mesh_westfirst 23

24 Flow Control Virtal Channels Coherence Protocol reqires certain nmber of virtal networks / message classes to avoid protocol deadlocks This is the minimm nmber of VCs reqired Within each vnet, there can be more than one VC for boosting network performance Credits In Garnet, only one packet can se a VC inside a roter at a time VCs in vnets carrying control messages are 1-flit deep VCs in vnets carrying data (cacheline) messages are 4-5 flit deep Each VC conveys its bffer availability by sending credits to its pstream roter 24

25 Conventional VC Roter Microarch FLIT V N 0 V N 1 Rote Compte VC 0 VC 1 VC n Inpt Bffers VC 1 VC 2 VC Allocator SW Allocator BW: Bffer Write RC: Rote Compte VA: VC Allocation Inpt VCs arbitrate for otpt VCs (Inpt VCs at next roter) SA: Switch Allocation Inpt ports arbitrate for otpt ports BR: Bffer Read VC n Inpt Bffers Crossbar Switch ST: Switch Traversal LT: Link Traversal BW RC VA SA BR ST LT 25

26 Single-Cycle Roter Implementation Roter.ccàwakep() Network Link.cc InptUnit.cc àwakep() SwitchAllocator.cc àwakep() * Arbitrate inports has_free_vc() OtptUnit.cc àwakep() Credit Link.cc VN0 VC 0 VC 1 VN1 VC 2 VC 3 VirtalChannel.cc * Bffer Write * Rote Compte 4 * Arbitrate otports * VC Allocate * send credit (schedle creditlink wakep next cycle) * Bffer Read (send flit to switch) select_free_vc() OtVCState.cc * Rcv Credit * Update State CreditLink.cc For mlti-cycle roter, add delay in flit before it can do SA CrossbarSwitch.ccàwakep() * Switch Traversal: Psh winner flits on link qee * Schedle otpt link wakep for next cycle NetworkLink.cc 26

27 Overview What are Networks-On-Chip (NoCs)? Why model NoCs accrately Garnet2.0 Configration Topology Roting Flow-Control Roter Microarchitectre System Integration Network Interface Network Parameters Rnning Garnet with Rby Rby Garnet Standalone Otpt Stats Extensions and FAQs 27

28 System Organization Rby Memory System GarnetNetwork.cc Coherence Protocol Network Interface Network Link Interface is MessageBffers from Rby Roter Roter Stats Credit Link 28

29 Network Interface Msg_size decides nmber of flits Can add additional info in flit Core + L1$ Dir NI Core + L1$ <VN, msg> Flitisize VC Select credit L2$ DMA NI NI NI R R NI R R NI L2$ Cache Controller VN0 VN1 VC 0 VC 1 VC 2 VC 3 Ingress To/From Roter L2$ Core + L1$ NI NI NI Dir NI Core + L1$ NI L2$ Egress NetworkInterface.cc àwakep() 29

30 Garnet Configrable Parameters ni_flit_size Defalt = 16B (128b) à 1-flit ctrl, 5-flit data This sets the bandwidth of each physical link vcs_per_vnet Total VCs in each inport = nm_vnets * vcs_per_vnet bffers_per_data_vc Defalt = 4 bffers_per_ctrl_vc Defalt = 1 roting_algorithm Weight-based table or cstom Defined in: src/mem/rby/network/garnet2.0/garnetnetwork.py 30

31 Command Line Parameters src/mem/rby/network/ BasicRoter.py BasicLink.py Network.py garnet2.0/garnetnetwork.py Definitions and Defalt Vales rby/rby.py configs/ common/options.py network/network.py example/garnet_synth_test.py - Overrides defalt vales in Rby - All parameters in in these.py files can be specified from command line 31

32 Rnning Garnet with Rby Bild Rby Coherence Protocol scons bild/x86_moesi_hammer/gem5.opt PROTOCOL=MOESI_hammer Protocol determines nmber of message classes/virtal networks reqired Invoke garnet2.0 from command line with appropriate network parameters./bild/x86_moesi_hammer/gem5.opt configs/example/fs.py --network=garnet2.0 --topology=mesh_xy... 32

33 Rnning Garnet Standalone Bild the Garnet_standalone protocol scons bild/null/gem5.debg PROTOCOL=Garnet_Standalone Dmmy protocol jst for traffic injection via Garnet Synthetic Traffic tester (next slide) 3 Virtal Networks: vnet 0 and vnet 1 inject ctrl (1-flit) packets, vnet 2 injects data (5-flit) packets Rn ser-specified synthetic traffic./bild/null/gem5.debg configs/example/garnet_synth_traffic.py --network=garnet2.0 --topology=... \ --synthetic=niform_random \ --injectionrate=0.01 \ --nm-packets-max=100 \ 33

34 Garnet Synthetic Traffic Dmmy CPU Model [only works with Garnet_standalone protocol] src/cp/testers/garnet_synthetic_traffic Inject packets for ser-specified traffic pattern at ser-specified injection rate niform_random tornado bit_complement bit_reverse bit_rotation neighbor shffle transpose Ability to inject continosly or fixed nmber of packets, and/or for fixed time, and/or from fixed sorce and/or to fixed destination in one/more vnets Heavy cstomization very sefl for debgging All parameters described here: 34

35 Overview What are Networks-On-Chip (NoCs)? Why model NoCs accrately Garnet2.0 Configration Topology Roting Flow-Control Roter Microarchitectre System Integration Network Interface Network Parameters Rnning Garnet with Rby Rby Garnet Standalone Otpt Stats Extensions and FAQs 35

36 Sample Simlation./bild/NULL/gem5.debg configs/example/garnet_synth_traffic.py --topology=mesh_xy --nm-cps=16 --nm-dirs=16 --mesh-rows=4 m5ot/config.ini 36

37 Otpt Stats m5ot/stats.txt Packet and Flit stats (#injected, #received, qeeing latency at NIC, and network latency) per VN and overall More stats can be added via GarnetNetwork.cc 37

38 Overview What are Networks-On-Chip (NoCs)? Why model NoCs accrately Garnet2.0 Configration Topology Roting Flow-Control Roter Microarchitectre System Integration Network Interface Network Parameters Rnning Garnet with Rby Rby Garnet Standalone Otpt Stats Extensions and FAQs 38

39 Extensions and FAQs System Level Modeling How can I integrate Garnet into my own simlator (or with the gem5 classic memory system)? This shold not be too hard - wold jst reqire some changes to the NI code on how it receives its inpts. If anyone wants to try it, I wold love to give pointers. How do I print a network trace? Yo can add some code to the NI. I have a patch on my website for reference. Can garnet read a network trace? Yo can rn Garnet in a standalone mode, and have it inject traffic from a trace instead of a fixed synthetic pattern. Alternately, try to se cp/testers/traffic_gen Does Garnet report NoC area and power nmbers? The otpt of Garnet can be fed into DSENT (Sn et al, NOCS 2012) which is present in ext/dsent. We will add an atomatic stats.txt parser for it soon. Can we model mltiple clock domains? The entire Rby memory system (inclding Garnet inside it) is one clock domain. To mimic a mlti-clock domain design, yo can schedle wakeps of slow roters intelligently at some mltiples of the clock rather than every cycle. 39

40 Extensions and FAQs Topology How do we model mltiple BW links in Garnet? Inherently, that wold reqire spport in the roter to manage mltiple flit sizes. Instead, yo can add mltiple links between the same nodes if yo want to model higher bandwidth. If they have the same weight, Garnet will randomly send over the two. Can we model a heterogeneos CPU-GPU system? Yes. The crrent AMD GPU model models a clster of CPUs connected to a GPU. Can we model indirect networks sch as Clos? Yes, there can be additional roters that are not connected to any controller and act prely as switches. Can we model large-scale HPC networks? Garnet can model any sized network. Yo can rn 256-node standalone simlations easily. However, beyond that gem5 cannot instantiate more directories (which it ses as destination nodes). I have a patch to rn node synthetic sims on my website. Bt these rn qite slowly. 40

41 Extensions and FAQs Roting How do we model an adaptive roting algorithm? If yo want to se internal NoC metrics (sch as nmber of credits at an otpt port) for making roting decisions, do not se table-based roting. Instead, set the roting-algorithm to cstom, and implement yor own roting fnction inside RotingUnit.cc. See otportcomptexy() for reference. Flow Control Can we implement alternate deadlock avoidance schemes (sch as escape VCs or dateline)? Yo can pdate the vc selection scheme inside SwitchAllocator to control which VCs get allocated. Microarchitectre Can we model variable nmber of VCs in each roter? Crrently the codebase is very tied to the global vcs_per_vnet parameter. If yo want to model variable nmber of VCs, one hack cold be to have everyone instantiate the same nmber of VCs, bt modify the VC select to never allocate certain VCs 41

42 Conclsions Garnet2.0 is an open-sorce research vehicle Use it and contribte to it! Being actively maintained by the following people Georgia Tech: Tshar Krishna AMD Research: Brad Beckmann, Onr Kayiran, Jieming Yin, Matt Porembas If yo have any qestions, on gem5-sers or gem5-dev mailing lists Wold love to have it integrated with the classic memory model Usefl Resorces: Thank yo! 42