12.07.2015 Views

NoC design and optimization for Multi-core media processors

NoC design and optimization for Multi-core media processors

NoC design and optimization for Multi-core media processors

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

LIST OF FIGURESxv4.12 FFT Benchmark. Energy per Instruction <strong>and</strong> Instructions per second 2 perWatt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904.13 Y1:PCT, Y2:on-chip transit <strong>and</strong> off-chip comm. times. . . . . . . . . . . . 924.14 FFT benchmark results. (Program Completion Time, comm.: communication). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924.15 FFT benchmark results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944.16 Program Completion Times. . . . . . . . . . . . . . . . . . . . . . . . . . . 954.17 Alternative Tile Placements, custom process scheduling example <strong>and</strong> idealinterconnect comparison results. Benchmark: FFT, L1: 256K, L2: 512K. . 985.1 (a) Process graph of a HiperLAN/2 baseb<strong>and</strong> processing SoC[7] <strong>and</strong> (b)<strong>NoC</strong> of the Object recognition processor[8]. . . . . . . . . . . . . . . . . . . 1035.2 A 64 Node, 8 × 8 2D LS-<strong>NoC</strong> along with <strong>NoC</strong> Manager interface to routingtables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075.3 Pipe establishment <strong>and</strong> label swapping example in a 3×3 LS-<strong>NoC</strong>. . . . . . 1095.4 LabelSwitchedRouterwithsinglecycleflittraversal. ValidsignalidentifiesData <strong>and</strong> Label as valid. PauseIn <strong>and</strong> PauseOut are flow control signals<strong>for</strong> downstream <strong>and</strong> upstream routers. Routing table has output port <strong>and</strong>label swap in<strong>for</strong>mation. Arbiter receives input from all the input portsalong with the flow control signal from the downstream router. . . . . . . . 1105.5 Label conflict at R1 resolved using Label swapping. il: Input Label, Dir:Direction, ol: Output Label. . . . . . . . . . . . . . . . . . . . . . . . . . . 1126.1 Surveillance system showing the application of LS-<strong>NoC</strong> in the Video computationserver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1246.2 A 2 router, 6 communicating nodes linear network. (b) <strong>Multi</strong>ple source,multiple sink flow calculation in a network. . . . . . . . . . . . . . . . . . . 1266.3 (a) Number of pipes in a linear network (Fig. 6.2(a)), lw = 3 bits, varyingconstraints. Constraint 1: Max 1 pipe per sink. (b) Max. number of pipesin 2D Mesh (Fig. 5.2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1277.1 (a) Process blocks of HiperLAN/2 baseb<strong>and</strong> processing SoC <strong>and</strong> Objectrecognition processor mapped on to a 8 × 8 LS-<strong>NoC</strong>. Pipe 1: PEC0 →PEC6, Pipe 2: MP → PEC3. (b) Flows set up <strong>for</strong> CBR & VBR traffic. . . 1317.2 Latency of HiperLAN/2 <strong>and</strong> ORP pipes in LS-<strong>NoC</strong> over varying injectionratesofnon-streamingapplicationnodes. Latencyofnon-provisionedpathsare titled (U). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1327.3 (a) Latency of CBR traffic over various injection rates of non-streamingnodes in LS-<strong>NoC</strong>. (b) Latency of VBR traffic over various injection ratesof non-streaming nodes in LS-<strong>NoC</strong>. . . . . . . . . . . . . . . . . . . . . . . 1337.4 LS-<strong>NoC</strong> being used alongside a best ef<strong>for</strong>t <strong>NoC</strong>. . . . . . . . . . . . . . . . 136B.1 Modules in LS-<strong>NoC</strong> router <strong>design</strong> shown along with testbench, implementedin Verilog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151B.2 Test cases used to verify an individual LS-<strong>NoC</strong> router. . . . . . . . . . . . 151

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!