CSCE 430/830 Computer Architecture Basic Pipelining & Performance

Name: CSCE 430/830 Computer Architecture Basic Pipelining & Performance
Uploaded: 2017-10-11T07:28:16+00:00
Duration: PTM42S10
Channel: Harry William Gregory
Description: CSCE 430/830 Computer Architecture Basic Pipelining & Performance

CSCE 430/830 Computer Architecture Basic Pipelining & Performance
Adopted from Professor David Patterson Electrical Engineering and Computer Sciences University of California, Berkeley CS252 S05

CSCE 430/830, Basic Pipelining & Performance
Outline MIPS – An ISA for Pipelining 5 stage pipelining Structural and Data Hazards Forwarding Branch Schemes Exceptions and Interrupts Conclusion 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

A "Typical" RISC ISA 32-bit fixed format instruction (3 formats) 32 32-bit GPR (R0 contains zero, DP take pair) 3-address, reg-reg arithmetic instruction Single address mode for load/store: base + displacement no indirection Simple branch conditions Delayed branch see: SPARC, MIPS, HP PA-Risc, DEC Alpha, IBM PowerPC, CDC 6600, CDC 7600, Cray-1, Cray-2, Cray-3 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Example: MIPS ( MIPS) Register-Register 31 26 25 21 20 16 15 11 10 6 5 Op Rs1 Rs2 Rd Opx Register-Immediate 31 26 25 21 20 16 15 immediate Op Rs1 Rd Branch 31 26 25 21 20 16 15 immediate Op Rs1 Rs2/Opx Jump / Call 31 26 25 target Op 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Datapath vs Control Datapath Controller signals Control Points Datapath: Storage, FU, interconnect sufficient to perform the desired functions Inputs are Control Points Outputs are signals Controller: State machine to orchestrate operation on the data path Based on desired function and signals 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Approaching an ISA Instruction Set Architecture Defines set of operations, instruction format, hardware supported data types, named storage, addressing modes, sequencing Meaning of each instruction is described by RTL (Register Transfer Language) on architected registers and memory Given technology constraints assemble adequate datapath Architected storage mapped to actual storage Function units to do all the required operations Possible additional storage (eg. MAR, MBR, …) Interconnect to move information among regs and FUs Map each instruction to sequence of RTLs Collate sequences into symbolic controller state transition diagram (STD) Lower symbolic STD to control points Implement controller 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

5 Steps of MIPS Datapath Figure A.2, Page A-8
Instruction Fetch Instr. Decode Reg. Fetch Execute Addr. Calc Memory Access Write Back Next PC MUX 4 Adder Next SEQ PC Zero? RS1 Reg File Address MUX Memory RS2 ALU Inst Memory Data L M D RD MUX MUX Sign Extend IR <= mem[PC]; PC <= PC + 4 Imm WB Data Reg[IRrd] <= Reg[IRrs1] opIRop Reg[IRrs2] 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Instruction Fetch Instr. Decode Reg. Fetch Execute Addr. Calc Memory Access Write Back Next PC IF/ID ID/EX MEM/WB EX/MEM MUX Next SEQ PC Next SEQ PC 4 Adder Zero? RS1 Reg File Address Memory MUX RS2 ALU RD Memory Data MUX MUX IR <= mem[PC]; PC <= PC + 4 Sign Extend Imm WB Data A <= Reg[IRrs1]; B <= Reg[IRrs2] RD RD RD rslt <= A opIRop B WB <= result 4/16/2017 CSCE 430/830, Basic Pipelining & Performance Reg[IRrd] <= WB CS252 S05

Inst. Set Processor Controller
IR <= mem[PC]; PC <= PC + 4 Ifetch A <= Reg[IRrs1]; B <= Reg[IRrs2] opFetch-DCD JSR JR ST PC <= IRjaddr if bop(A,b) PC <= PC+IRim br jmp r <= A + IRim WB <= Mem[r] Reg[IRrd] <= WB LD r <= A opIRop IRim Reg[IRrd] <= WB WB <= r RI RR r <= A opIRop B WB <= r Reg[IRrd] <= WB CSCE 430/830, Basic Pipelining & Performance CS252 S05

Instruction Fetch Instr. Decode Reg. Fetch Execute Addr. Calc Memory Access Write Back Next PC IF/ID ID/EX MEM/WB EX/MEM MUX Next SEQ PC Next SEQ PC 4 Adder Zero? RS1 Reg File Address Memory MUX RS2 ALU Memory Data MUX MUX Sign Extend Imm WB Data RD RD RD Data stationary control local decode for each instruction phase / pipeline stage 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Visualizing Pipelining Figure A.2, Page A-8
Time (clock cycles) Reg ALU DMem Ifetch Cycle 1 Cycle 2 Cycle 3 Cycle 4 Cycle 6 Cycle 7 Cycle 5 I n s t r. O r d e 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Instruction-Level Parallelism
Review of Pipelining (the laundry analogy) 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Pipelining is not quite that easy!
Limits to pipelining: Hazards prevent next instruction from executing during its designated clock cycle Structural hazards: HW cannot support this combination of instructions (single person to fold and put clothes away) Data hazards: Instruction depends on result of prior instruction still in the pipeline (missing sock) Control hazards: Caused by delay between the fetching of instructions and decisions about changes in control flow (branches and jumps). 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

One Memory Port/Structural Hazards Figure A.4, Page A-14
Time (clock cycles) Cycle 1 Cycle 2 Cycle 3 Cycle 4 Cycle 5 Cycle 6 Cycle 7 ALU I n s t r. O r d e Load Ifetch Reg DMem Reg Reg ALU DMem Ifetch Instr 1 Reg ALU DMem Ifetch Instr 2 ALU Instr 3 Ifetch Reg DMem Reg Reg ALU DMem Ifetch Instr 4 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

One Memory Port/Structural Hazards (Similar to Figure A.5, Page A-15)
Time (clock cycles) Cycle 1 Cycle 2 Cycle 3 Cycle 4 Cycle 5 Cycle 6 Cycle 7 ALU I n s t r. O r d e Load Ifetch Reg DMem Reg Reg ALU DMem Ifetch Instr 1 Reg ALU DMem Ifetch Instr 2 Bubble Stall Reg ALU DMem Ifetch Instr 3 How do you “bubble” the pipe? 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Speed Up Equation for Pipelining
For simple RISC pipeline, CPI = 1: 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Example: Dual-port vs. Single-port
Machine A: Dual ported memory (“Harvard Architecture”) Machine B: Single ported memory, but its pipelined implementation has a 1.05 times faster clock rate Ideal CPI = 1 for both Loads are 40% of instructions executed SpeedUpA = Pipeline Depth/(1 + 0) x (clockunpipe/clockpipe) = Pipeline Depth SpeedUpB = Pipeline Depth/( x 1) x (clockunpipe/(clockunpipe / 1.05) = (Pipeline Depth/1.4) x 1.05 = 0.75 x Pipeline Depth SpeedUpA / SpeedUpB = Pipeline Depth/(0.75 x Pipeline Depth) = 1.33 Machine A is 1.33 times faster 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Data Hazard on R1 Figure A.6, Page A-17
Time (clock cycles) IF ID/RF EX MEM WB I n s t r. O r d e add r1,r2,r3 sub r4,r1,r3 and r6,r1,r7 or r8,r1,r9 xor r10,r1,r11 Reg ALU DMem Ifetch 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Three Generic Data Hazards
Read After Write (RAW) InstrJ tries to read operand before InstrI writes it Caused by a “Dependence” (in compiler nomenclature). This hazard results from an actual need for communication. I: add r1,r2,r3 J: sub r4,r1,r3 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Write After Read (WAR) InstrJ writes operand before InstrI reads it Called an “anti-dependence” by compiler writers. This results from reuse of the name “r1”. Can it happen in MIPS 5 stage pipeline? All instructions take 5 stages, and Reads are always in stage 2, and Writes are always in stage 5 I: sub r4,r1,r3 J: add r1,r2,r3 K: mul r6,r1,r7 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Write After Write (WAW) InstrJ writes operand before InstrI writes it. Called an “output dependence” by compiler writers This also results from the reuse of name “r1”. Can’t happen in MIPS 5 stage pipeline because: All instructions take 5 stages, and Writes are always in stage 5 Will see WAR and WAW in more complicated pipes I: sub r1,r4,r3 J: add r1,r2,r3 K: mul r6,r1,r7 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Forwarding to Avoid Data Hazard Figure A.7, Page A-19
Time (clock cycles) I n s t r. O r d e add r1,r2,r3 sub r4,r1,r3 and r6,r1,r7 or r8,r1,r9 xor r10,r1,r11 Reg ALU DMem Ifetch 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

HW Change for Forwarding Figure A.23, Page A-37
ID/EX EX/MEM MEM/WR NextPC mux Registers ALU Data Memory mux mux Immediate What circuit detects and resolves this hazard? 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Forwarding to Avoid LW-SW Data Hazard Figure A.8, Page A-20
Time (clock cycles) I n s t r. O r d e add r1,r2,r3 lw r4, 0(r1) sw r4,12(r1) or r8,r6,r9 xor r10,r9,r11 Reg ALU DMem Ifetch Any hazard that cannot be avoided with forwarding? 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Data Hazard Even with Forwarding Figure A.9, Page A-21
Time (clock cycles) Reg ALU DMem Ifetch I n s t r. O r d e lw r1, 0(r2) sub r4,r1,r6 and r6,r1,r7 or r8,r1,r9 MIPS actutally didn’t interlecok: MPU without Interlocked Pipelined Stages 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Data Hazard Even with Forwarding (Similar to Figure A.10, Page A-21)
Time (clock cycles) I n s t r. O r d e Reg ALU DMem Ifetch lw r1, 0(r2) How is this detected? Reg Ifetch ALU DMem Bubble sub r4,r1,r6 Ifetch ALU DMem Reg Bubble and r6,r1,r7 Bubble Ifetch Reg ALU DMem or r8,r1,r9 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Software Scheduling to Avoid Load Hazards
Try producing fast code for a = b + c; d = e – f; assuming a, b, c, d ,e, and f in memory. Slow code: LW Rb,b LW Rc,c ADD Ra,Rb,Rc SW a,Ra LW Re,e LW Rf,f SUB Rd,Re,Rf SW d,Rd Fast code: LW Rb,b LW Rc,c LW Re,e ADD Ra,Rb,Rc LW Rf,f SW a,Ra SUB Rd,Re,Rf SW d,Rd Compiler optimizes for performance. Hardware checks for safety. 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Outline Review Quantify and summarize performance Ratios, Geometric Mean, Multiplicative Standard Deviation F&P: Benchmarks age, disks fail,1 point fail danger MIPS – An ISA for Pipelining 5 stage pipelining Structural and Data Hazards Forwarding Branch Schemes Exceptions and Interrupts Conclusion 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Control Hazard on Branches Three Stage Stall
Reg ALU DMem Ifetch 10: beq r1,r3,36 14: and r2,r3,r5 18: or r6,r1,r7 22: add r8,r1,r9 36: xor r10,r1,r11 What do you do with the 3 instructions in between? How do you do it? Where is the “commit”? 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Branch Stall Impact If CPI = 1, 30% branch, Stall 3 cycles => new CPI = 1.9! Two part solution: Determine branch outcome sooner, AND Compute taken branch (target) address earlier MIPS branch tests if register = 0 or  0 MIPS Solution: Move Zero test to ID/RF stage Adder to calculate new PC in ID/RF stage 1 clock cycle penalty for branch versus 3 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Pipelined MIPS Datapath Figure A.24, page A-38
Instruction Fetch Instr. Decode Reg. Fetch Execute Addr. Calc Memory Access Write Back Next PC Next SEQ PC ID/EX EX/MEM MEM/WB MUX 4 Adder IF/ID Adder Zero? RS1 Address Reg File Memory RS2 ALU Memory Data MUX MUX Sign Extend Imm WB Data RD RD RD Interplay of instruction set design and cycle time. 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Four Branch Hazard Alternatives
#1: Stall until branch direction is clear #2: Predict Branch Not Taken Execute successor instructions in sequence “Squash” instructions in pipeline if branch actually taken Advantage of late pipeline state update 47% MIPS branches not taken on average PC+4 already calculated, so use it to get next instruction #3: Predict Branch Taken 53% MIPS branches taken on average But haven’t calculated branch target address in MIPS MIPS still incurs 1 cycle branch penalty Other machines: branch target known before outcome 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Four Branch Hazard Alternatives
#4: Delayed Branch Define branch to take place AFTER a following instruction branch instruction sequential successor1 sequential successor sequential successorn branch target if taken 1 slot delay allows proper decision and branch target address in 5 stage pipeline MIPS uses this Branch delay of length n 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Scheduling Branch Delay Slots (Fig A.14)
A. From before branch B. From branch target C. From fall through add $1,$2,$3 if $2=0 then add $1,$2,$3 if $1=0 then sub $4,$5,$6 delay slot delay slot add $1,$2,$3 if $1=0 then delay slot sub $4,$5,$6 becomes becomes becomes if $2=0 then add $1,$2,$3 add $1,$2,$3 if $1=0 then sub $4,$5,$6 add $1,$2,$3 if $1=0 then sub $4,$5,$6 Limitations on delayed-branch scheduling come from 1) restrictions on the instructions that can be moved/copied into the delay slot and 2) limited ability to predict at compile time whether a branch is likely to be taken or not. In B and C, the use of $1 prevents the add instruction from being moved to the delay slot In B the sub may need to be copied because it could be reached by another path. B is preferred when the branch is taken with high probability (such as loop branches A is the best choice, fills delay slot In B, the sub instruction may need to be copied, increasing IC In B and C, must be okay to execute sub when branch fails 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Delayed Branch Compiler effectiveness for single branch delay slot: Fills about 60% of branch delay slots About 80% of instructions executed in branch delay slots useful in computation About 50% (60% x 80%) of slots usefully filled Delayed Branch downside: As processor go to deeper pipelines and multiple issue, the branch delay grows and need more than one delay slot Delayed branching has lost popularity compared to more expensive but more flexible dynamic approaches Growth in available transistors has made dynamic approaches relatively cheaper 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Evaluating Branch Alternatives
Assume 4% unconditional branch, 6% conditional branch- untaken, 10% conditional branch-taken Scheduling Branch CPI speedup v. speedup v. scheme penalty unpipelined stall Stall pipeline Predict taken Predict not taken Delayed branch 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

More branch evaluations
Suppose the branch frequencies (as percentage of all instructions) of 15% cond. Branches, 1% jumps and calls, and 60% cond. Branches are taken. Consider a 4-stage pipeline where branch is resolved at the end of the 2nd cycle for uncond. Branches and at the end of the 3rd cycle for cond. Branches. How much faster would the machine be without any branch hazards, ignoring other pipeline stalls? Pipeline speedupideal = Pipeline depth/(1+Pipeline stalls) = 4/(1+0) = 4 Pipeline stallsreal = (1x1%) + (2x9%) + (1x6%) = 0.24 Pipeline speedupreal = 4/(1+0.24) = 3.23 Pipeline speedupwithout control hazards = 4/3.23 = 1.24 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

More branch question A reduced hardware implementation of the classic 5-stage RISC pipeline might use the EX stage hardware to perform a branch instruction comparison and then not actually deliver the branch target PC to the IF stage until the clock cycle in which the branch reaches the MEM stage. Control hazard stalls can be reduced by resolving branch instructions in ID, but improving performance in one aspect may reduce performance in other circumstances. How does determining branch outcome in the ID stage have the potential to increase data hazard stall cycles? 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Problems with Pipelining
Exception: An unusual event happens to an instruction during its execution Examples: divide by zero, undefined opcode Interrupt: Hardware signal to switch the processor to a new instruction stream Example: a sound card interrupts when it needs more audio output samples (an audio “click” happens if it is left waiting) Problem: It must appear that the exception or interrupt must appear between 2 instructions (Ii and Ii+1) The effect of all instructions up to and including Ii is totally complete No effect of any instruction after Ii can take place The interrupt (exception) handler either aborts program or restarts at instruction Ii+1 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

Precise Exceptions in Static Pipelines
Key observation: architected state only change in memory and register write stages. 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

And In Conclusion: Control and Pipelining
Quantify and summarize performance Ratios, Geometric Mean, Multiplicative Standard Deviation F&P: Benchmarks age, disks fail,1 point fail danger Next time: Read Appendix A, record bugs online! Control VIA State Machines and Microprogramming Just overlap tasks; easy if tasks are independent Speed Up  Pipeline Depth; if ideal CPI is 1, then: Hazards limit performance on computers: Structural: need more HW resources Data (RAW,WAR,WAW): need forwarding, compiler scheduling Control: delayed branch, prediction Exceptions, Interrupts add complexity Next time: Read Appendix C, record bugs online! 4/16/2017 CSCE 430/830, Basic Pipelining & Performance CS252 S05

CSCE 430/830 Computer Architecture Basic Pipelining & Performance

Similar presentations

Presentation on theme: "CSCE 430/830 Computer Architecture Basic Pipelining & Performance"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

CSCE 430/830 Computer Architecture Basic Pipelining & Performance

Similar presentations

Presentation on theme: "CSCE 430/830 Computer Architecture Basic Pipelining & Performance"— Presentation transcript:

Similar presentations

About project

Feedback