10/24/05 ELEC62001 Kasi L.K. Anbumony Department of Electrical and Computer Engineering Auburn University Auburn, AL Superscalar Processors
10/24/05 ELEC62002 Pipelining: Motivation Pipeline Hazards Advanced Pipelining –Instruction Level Parallelism (ILP) –Multiple Issue (MIPS Superscalar) Static Multiple Issue (SW centric) Dynamic Multiple Issue (HW centric) Superscalar Processor Conclusion Outline
10/24/05 ELEC62003 Multiple instructions are overlapped in execution. To exploit the Instruction level parallelism(ILP) One of technique to make the processors fast Some terms: Stages Task Order Throughput In pipeline the stages occur concurrently (or) parallely Possible as long as we have separate resources for each stage Pipelining: Motivation
10/24/05 ELEC62004 Sequential Laundry: Non-pipelined Sequential laundry takes 6 hours for 4 loads If they learned pipelining, how long would laundry take? TaskOrderTaskOrder A B C D 6 PM Midnight Time
10/24/05 ELEC62005 Pipelined Laundry:Start work ASAP Pipelined laundry takes 3.5 hours for 4 loads TaskOrderTaskOrder 6 PM Midnight Time 20 A B C D 30 40
10/24/05 ELEC62006 Pipelining: Lessons Improvement in throughput of entire workload without improving any time to complete a single load Pipeline rate limited by slowest pipeline stage Multiple tasks operating simultaneously Potential speedup = Number pipe stages Unbalanced lengths of pipe stages reduces speedup Time to “fill” pipeline and time to “drain” it reduces speedup TaskOrderTaskOrder 6 PM 789 Time 20 A B C D 30 40
10/24/05 ELEC62007 Comparison: Example Consider a non-pipelined machine with 5 execution steps of lengths 200 ps, 100 ps, 200 ps, 200 ps, and 100 ps. Due to clock skew and setup, pipelining adds 5 ps of overhead to each instruction stage. Ignoring latency impact, how much speedup in the instruction execution rate will we gain from a pipeline?
10/24/05 ELEC62008 Sequential vs. Pipelined Execution Pipelined Execution Sequential Execution
10/24/05 ELEC62009 Speed Up Equation for Pipelining Speedup from pipelining= = Ideal CPI pipelined = CPI unpipelined /Pipeline depth Speedup =
10/24/05 ELEC Speed Up Equation for Pipelining
10/24/05 ELEC It’s Not That Easy for Computers: Limitation Limits to pipelining: Hazards prevent next instruction from executing during its designated clock cycle –Structural hazards: Hardware cannot support this combination of instructions that has to be executed in the same clock cycle (washer+dryer) –Data hazards: Instruction depends on result of prior instruction still in pipeline (one sock missing) –Control hazards: Pipelining of branches & other instructions. Common solution is to stall the pipeline until the hazard “bubbles” through the pipeline
10/24/05 ELEC Instruction Level Parallelism Longer pipeline Laundry analogy: Divide our washer into three machines that perform the wash, rinse and spin steps of a traditional machine To get the full speedup,we need to rebalance the remaining steps so that they are of the same length Amount of parallelism exploited is higher, since there are more operations being overlapped
10/24/05 ELEC Advanced Pipelining: Techniques Motivation: To further exploit the Instruction Level Parallelism (ILP) Multiple Issue Replicate the internal components of the computer so that it can launch multiple instructions in every pipeline stage Dynamic Pipeline scheduling (or) Dynamic Pipelining (or) Dynamic Multiple issue by hardware to avoid pipeline hazards
10/24/05 ELEC Multiple Issue: Superscalar Launch multiple instructions in parallel A Superscalar laundry would replace our household washer and dryer with say, three washers and three dryers. Also followed by 3 assistants to fold and put away thee times as much laundry in the same amount of time. Downside extra work needed to keep all the machines busy and transferring load to next pipeline stage. Superscalar is defined as executing more than one instruction per clock cycle
10/24/05 ELEC Performance Metrics: CPI & IPC Instruction execution rate exceed the clock rate Example: 6GHz, 4-way multiple-issue microprocessor can execute at a peak rate of 24 billion instructions per second and have a best case of CPI of 0.25 Instructions per clock cycle (IPC) (for the above case: 4) Assume a 5 stage pipeline such a processor would have 20 instructions in execution at any given time.
10/24/05 ELEC Multiple issue processor: Decision Strategy Static Multiple Issue Decisions are made at compile time before execution Software based Compiler scheduling VLIW(Very Long Instruction Word) Dynamic Multiple Issue Decisions are made at run/execution time by the processor Dynamic scheduling Hardware based
10/24/05 ELEC Static Multiple Issue Processor Issue Packet: Set of instructions which can be paired to form one large instruction with multiple operations (VLIW) Relies on Compiler to take on responsibilities for handling data and control hazards Some of the compiler’s responsibilities may be static branch prediction and code scheduling
10/24/05 ELEC Getting CPI < 1:Static 2 Issue pipeline Superscalar MIPS: 2 instructions, 1 ALU & 1 LOAD instruction – Fetch 64-bits/clock cycle; ALU on left, Load on right – Can only issue 2nd instruction if 1st instruction issues TypePipeStages ALU instructionIFIDEXMEMWB Load instructionIFIDEXMEMWB ALU instructionIFIDEXMEMWB Load instructionIFIDEXMEMWB ALU instructionIFIDEXMEMWB Load instructionIFIDEXMEMWB
10/24/05 ELEC Static Multiple Issue: Datapath IM Reg. file ALU ALU/bx xion lw/sw xion
10/24/05 ELEC Example: Multiple Issue code scheduling Loop: lw $t0, 0($s1) addu $t0, $t0, $s2 sw $t0, 0 ($s1) addi $s1, $s1, -4 bne $s1,$zero, Loop After reordering the instructions based on dependencies, we get a CPI=0.8 (or) IPC=1.25 ALU/BXlw/swClock cycle Loop:lw $t0, 0($s1)1 addi $s1, $s1, -42 addu $t0, $t0, $s23 bne $s1,$zero, Loopsw $t0, 0 ($s1)4
10/24/05 ELEC Loop Unrolling: 4 Iterations Multiple copies of the loop body are made, thus more ILP by overlapping instructions from different iterations CPI=8/14=0.57 ALU/BXlw/swClock cycle Loop:addi $s1, $s1, -16lw $t0, 0($s1)1 lw $t1, 12($s1)2 addu $t0, $t0, $s2lw $t2, 8($s1)3 addu $t1, $t1, $s2lw $t3, 4($s1)4 addu $t2, $t2, $s2sw $t0, 16 ($s1)5 addu $t3, $t3, $s2sw $t0, 12 ($s1)6 sw $t0, 8 ($s1)7 bne $s1,$zero, Loopsw $t0, 4 ($s1)8
10/24/05 ELEC Dynamic Multiple-Issue Processors Instructions are issue in order and the processor decides whether zero,one (or) more instructions can issue in a given clock cycle Again achieving good performance requires the compiler to schedule instructions to move dependencies apart and thereby improving the instruction issue rate
10/24/05 ELEC Dynamic Scheduling: Definition Dynamic pipeline scheduling goes past stalls to find later instructions to execute while waiting for the stall to be resolved Chooses which instruction to execute next by reordering the instructions to avoid stalls (dynamic issue decisions) lw $t0, 20($s2) addu $t1, $t0, $s2 sub $s4, $s4, $t3 slti $t5, $s4, 20 bne $s1,$zero, Loop
10/24/05 ELEC HW Schemes: Why? Why in HW at run time? –Works when can’t know real dependence at compile time –Compiler simpler –Code for one machine runs well on another
10/24/05 ELEC Dynamic Pipeline Scheduling: Model Inst. Fetch & decode unit Res. station Integer FP lw/sw Reorder buffer Commit unit Res. station ……….. In order Out order
10/24/05 ELEC HW Units: Working Inst fetch/decode unit fetches instructions,decodes them and sends each instruction to a corresponding functional unit of the execute stage 5-10 functional units with buffers called reservation stations that holds the operands and operation As soon as buffer contains all the operands, functional unit executes, the result is calculated It is for the commit unit to decide when it is safe to put the result into the register file (or) for store into memory
10/24/05 ELEC Dynamic scheduling: in-order completion To make programs behave as if they run on a non-pipelined computer, the instruction fetch and decode unit is required to issue instructions in order, and the commit unit is required to write results to registers and memory in program execution order (in-order completion) Hence an exception occurs, the computer can point to the last instruction executed and the only registers updated will be all those written by the instructions before exception
10/24/05 ELEC Dynamic scheduling: Speculation Speculative execution: Dynamic scheduling can be combined with branch prediction, so after a mispredicted branch, commit unit be able to discard all the results in the execution unit Dynamic scheduling can also be combined with Superscalar execution, so each unit may be committing 4 to 6 instructions per cycle
10/24/05 ELEC Superscalar Processor
10/24/05 ELEC Conclusion: Several Steps ILP Exploitation
10/24/05 ELEC References Computer Organization & Design, Patterson & Hennessy, 2 & 3 Edition mlhttp:// ml %20lecture%204-05f.ppt (Pipelining) 116%20lecture%204-05f.ppt