impact of cmos technologies scaling in leakage reduction
play

Impact of CMOS Technologies scaling in Leakage Reduction Techniques - PowerPoint PPT Presentation

Impact of CMOS Technologies scaling in Leakage Reduction Techniques Saad Arrabi, Taeyoung Kim OUTLINE INTRODUCTION BACKGROUND METHODOLOGIES SIMULATION RESULTS CONTRIBUTION FUTURE WORK INTRODUCTION MOTIVATION Power


  1. Impact of CMOS Technologies scaling in Leakage Reduction Techniques Saad Arrabi, Taeyoung Kim

  2. OUTLINE • INTRODUCTION • BACKGROUND • METHODOLOGIES • SIMULATION RESULTS • CONTRIBUTION • FUTURE WORK

  3. INTRODUCTION • MOTIVATION – Power consumption is the major concern in CMOS semiconductor industries. Leakage is one of the big part of power consumption. – Off current leakage is being more serious problem as the technology size shrinks. • GOALS – Explore what conventional techniques for leakage reduction is used. – Investigate how effectively they can cope with new technology scaling.

  4. BACKGROUND Sleep Stack Zigzag CMOS Sleepy Stack

  5. Sleep • NMOS Sleep transistor usually used – To reduce resistance of “on” status • Pros – Reduction dynamic and leakage power • Cons – Reduce performance and requires additional area – Energy is consumed by charging and discharging the virtual rails • Knob – Footer vs. Header – Width – Sharing vs. Non-sharing Sleep TR • Sharing will decrease the delay

  6. STACK • Doesn’t need to go to sleep mode • Introduces new capacitance and delay • Knobs – Width: more width, more leakage, more area, less delay – Placement: Headers only, some inputs. • Different leakage reduction and less area

  7. Methodologies • RANDOM CIRCUIT – Simulate glitching – Large enough to be between 2 registers stages – Not fully accurate, but good enough • DELAY – Dynamic Delay, 50% of input to 50% of output – Wake up Delay, 50% of input signal to 90% of rail voltage • ENERGY – Dynamic Energy, averaged between 0->1, 1->0 – Leakage Energy, averaged between static 0, 1 – Wake up Energy, same as delay

  8. Dynamic Power vs Total Widths 3 22nm Shared Sleep 32nm Shared Sleep 45nm Shared Sleep 65nm Shared Sleep 2.5 22nm Non-shared Sleep 32nm Non-shared Sleep 45nm Non-shared Sleep 65nm Non-shared Sleep Dynamic Power (Nomalized by BASECASE) 22nm Stack 2 32nm Stack 45nm Stack 65nm Stack 1.5 1 0.5 0 1 2 3 4 5 Total Width (x Minimun)

  9. Dynamic Delay vs. Total Widths 7 22nm Shared Sleep 32nm Shared Sleep 6 45nm Shared Sleep 65nm Shared Sleep 22nm Non-shared Sleep 32nm Non-shared Sleep 45nm Non-shared Sleep 5 65nm Non-shared Sleep 22nm Stack Delay (Normalized by BASECASE) 32nm Stack 45nm Stack 65nm Stack 4 3 2 1 0 1 2 3 4 5 Total Width (x Minimum)

  10. Leakage reduction variation 22 nm leakage variation 8 6 Occurrences 4 share 2 noshare 0 stack -2 0.00 0.05 0.10 0.15 0.20 0.25 0.30 Leakage reduction normalized 65 nm leakage variation 10 Occurrences 5 share noshare 0 stack 0.00 0.50 1.00 1.50 2.00 -5 Leakage reduction normalized

  11. Comparison Metric Stack Sleep Added delay High Medium Added energy High Low Leakage in active mode Medium None Leakage in sleep Medium High Complexity Simple Complex Area Big area Medium area

  12. Contribution • Showed the effectiveness of some techniques for future technologies • Provide a base work for knob tweaking for leakage reduction techniques • Provided pareto curve methodology for leakage and delay

  13. Future Work • Analysis of the other techniques using more general circuit, such as full adder and SRAM. • Analysis of different set of knobs like placement location and voltage threshold. • Evaluation of new scaling technologies (16nm) or using other Predictive Technology Model. • Use different cost formulas like complexity

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend