pipelining - university of california, san...

27
Pipelining 1

Upload: others

Post on 20-Oct-2019

3 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

Pipelining

1

Page 2: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

Today

• Quiz• Introduction to pipelining

2

Page 3: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

Pipelining

Logic (10ns)

Latc

Latc

Logic (10ns)

Latc

Latc

Logic (10ns)

Latc

Latc

What’s the latency for one unit of work?

What’s the throughput?

10ns

20ns

30ns

Page 4: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

Pipelining1.Break up the logic with latches into “pipeline stages”2.Each stage can act on different data3.Latches hold the inputs to their stage4.Every clock cycle data transfers from one pipe stage to

the next

Logic (10ns)

Latc

Latc

Logic(2ns)

Latc

Latc

Logic(2ns)

Latc

Logic(2ns)

Latc

Logic(2ns)

Latc

Logic(2ns)

Latc

Page 5: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

Logic Logic Logic Logic Logic

Logic Logic Logic Logic Logic

Logic Logic Logic Logic Logic

Logic Logic Logic Logic Logic

Logic Logic Logic Logic Logic

Logic Logic Logic Logic Logic

2ns4ns6ns8ns10ns12nsWhat’s the latency for one

unit of work?What’s the throughput?

Page 6: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

• Critical path is the longest possible delay between two registers in a design.

• The critical path sets the cycle time, since the cycle time must be long enough for a signal to traverse the critical path.

• Lengthening or shortening non-critical paths does not change performance

• Ideally, all paths are about the same length

6

Critical path review

Logic

Page 7: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

7

Pipelining and Logic

Logic

Logic

Logic

Logic

Logic

Logic

Logic

Logic

Logic

Logic

Logic

Logic

• Hopefully, critical path reduced by 1/3

Page 8: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

• You cannot pipeline forever• Some logic cannot be pipelined arbitrarily -- Memories• Some logic is inconvenient to pipeline.• How do you insert a register in the middle of an adder?

• Registers have a cost• They cost area -- choose “narrow points” in the logic• They cost time

• Extra logic delay• Set-up and hold times.

Limits on Pipelining

8

Logic

Logic

Logic

Logic

Logic

Logic

Page 9: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

Pipelining Overhead

• Logic Delay (LD) -- How long does the logic take (i.e., the useful part)

• Set up time (ST) -- How long before the clock edge do the inputs to a register need be ready?

• Register delay (RD) -- Delay through the internals of the register.

• BaseCT -- cycle time before pipelining• BaseCT = LD + ST + RD.• Total delay = BaseCT

• PipeCT -- cycle time after pipelining N times• PipeCT = ?• Total delay = ?

9

Page 10: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

Pipelining Overhead

• Logic Delay (LD) -- How long does the logic take (i.e., the useful part)

• Set up time (ST) -- How long before the clock edge do the inputs to a register need be ready?

• Register delay (RD) -- Delay through the internals of the register.

• BaseCT -- cycle time before pipelining• BaseCT = LD + ST + RD.

• PipeCT -- cycle time after pipelining N times• PipeCT = ST + RD + LD/N• Total time = N*ST + N*RD + LD

10

Page 11: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

• You cannot put registers just anywhere• You may not have access to the internal of some block• Ex: memories

• Balancing the path lengths is challenging• The there are many more potential critical paths in a

pipelined design.

Pipelining Difficulties

11

Page 12: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

• The critical path only went down a bit.

Pipelining Difficulties

12

Fast

Logic

Slow Logic

Slow Logic

Fast

Logic

Fast

Logic

Slow Logic

Slow Logic

Fast

Logic

Page 13: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

How to pipeline a processor

• Break each instruction into pieces -- remember the basic algorithm for execution• Fetch• Decode• Collect arguments• Execute• Write back results• Compute next PC

• The “classic 5-stage MIPS pipeline”• Fetch -- read the instruction• Decode -- decode and read from the register file• Execute -- Perform arithmetic ops and address calculations• Memory -- access data memory.• Write back-- Store results in the register file.

13

Page 14: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

14

Pipelining a processor

EX

DecodeFetch Mem Write

back

EX

DecodeFetch Mem Write

back

Page 15: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

• Break the processor into P pipe stages

• What happens to latency?• L = Inst * CPI * CycleTime

• The cycle time = ?

• CPI = ?

15

Impact of Pipelining

Page 16: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

• Break the processor into P pipe stages

• What happens to latency?• L = Inst * CPI * CycleTime

• The cycle time = CT/P

• CPI = 1• CPI is an average: Cycles/instructions• When # of instructions is large, CPI = 1• If just one instruction, CPI = P

16

Impact of Pipelining

Page 17: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

Pipelined Datapath

ReadAddress

Instruc(onMemory

Add

PC

4

Write Data

Read Addr 1

Read Addr 2

Write Addr

Register

File

Read Data 1

Read Data 2

16 32

ALU

Shi<le< 2

Add

DataMemory

Address

Write Data

ReadData

SignExtend

Page 18: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

Pipelined Datapath

ReadAddress

Instruc(onMemory

Add

PC

4

Write Data

Read Addr 1

Read Addr 2

Write Addr

Register

File

Read Data 1

Read Data 2

16 32

ALU

Shi<le< 2

Add

DataMemory

Address

Write Data

ReadData

IFetch/D

ec

Dec/Exec

Exec/M

em

Mem

/WB

SignExtend

Page 19: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

Pipelined Datapath

ReadAddress

Instruc(onMemory

Add

4

Write Data

Read Addr 1

Read Addr 2

Write Addr

Register

File

Read Data 1

Read Data 2

16 32

ALU

Shi<le< 2

Add

DataMemory

Address

Write Data

ReadData

SignExtend

add …lw …Sub…Sub ….Add …Add …

Page 20: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

Pipelined Datapath

ReadAddress

Instruc(onMemory

Add

4

Write Data

Read Addr 1

Read Addr 2

Write Addr

Register

File

Read Data 1

Read Data 2

16 32

ALU

Shi<le< 2

Add

DataMemory

Address

Write Data

ReadData

SignExtend

add …lw …Sub…Sub ….Add …Add …

Page 21: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

Pipelined Datapath

ReadAddress

Instruc(onMemory

Add

4

Write Data

Read Addr 1

Read Addr 2

Write Addr

Register

File

Read Data 1

Read Data 2

16 32

ALU

Shi<le< 2

Add

DataMemory

Address

Write Data

ReadData

SignExtend

add …lw …Sub…Sub ….Add …Add …

Page 22: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

Pipelined Datapath

ReadAddress

Instruc(onMemory

Add

4

Write Data

Read Addr 1

Read Addr 2

Write Addr

Register

File

Read Data 1

Read Data 2

16 32

ALU

Shi<le< 2

Add

DataMemory

Address

Write Data

ReadData

SignExtend

add …lw …Sub…Sub ….Add …Add …

Page 23: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

Pipelined Datapath

ReadAddress

Instruc(onMemory

Add

4

Write Data

Read Addr 1

Read Addr 2

Write Addr

Register

File

Read Data 1

Read Data 2

16 32

ALU

Shi<le< 2

Add

DataMemory

Address

Write Data

ReadData

SignExtend

add …lw …Subi…Sub ….Add …Add …

Page 24: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

Simple Pipelining Control

24

EX

DecodeFetch Mem Write

back

Fetch

Fetch

EX

DecodeFetch Mem Write

back

Fetch Fetch Fetch

• Compute all the control bits in decode, then pass them from stage to stage. It won’t stay this simple...

Page 25: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

Pipelining is Tricky

• If all the data flows in one direction, pipelining is relatively easy.

• Not so, for processors. • Decode and write back both access the register file.• Branch instructions affect the next PC• Instructions need values computed by previous

instructions

25

Page 26: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

Not just tricky, Hazardous!

• Hazards are situations where pipelining does not work as elegantly as we would like• Caused by backward flowing signals• Or by lack of available hardware

• Three kinds• Data hazards -- an input is not available on the cycle it is

needed• Control hazards -- the next instruction is not known• Structural hazards -- we have run out of a hardware

resource

• Detecting, avoiding, and recovering from these hazards is what makes processor design hard.• That, and the Xilinx tools ;-)

26

Page 27: Pipelining - University of California, San Diegocseweb.ucsd.edu/classes/sp09/cse141/Slides/05_Pipelining.pdf · Pipelining 1.Break up the logic with latches into “pipeline stages”

A Structural Hazard

• Both the decode and write back stage have to access the register file.

• There is only one registers file. A structural hazard!!

• Solution: Write early, read late• Writes occur at the clock edge and complete long

before the end of the cycle• This leave enough time for the outputs to settle for the

reads.

• Hazard avoided!

•27

EX

DecodeFetch Mem Write

back