F6: Power/performance optimization of many-core processor SoCs

Stephen Kosonocky, Vladimir Stojanovic, Kees Van Berkel, Ming Yang Chao, Tobias Knoll, Joshua Friedrich

Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

1 Citation (Scopus)

Abstract

As performance scaling per core continues to slow-down, designers are faced with a myriad of challenges in efficiently using the transistors available in modern processes. This Forum will address these next generation computing challenges in the context of highly-parallel manycore processors. The key design challenge in this manycore era is management and efficient use of resources across the layers of design hierarchy to provide power efficient high performance. System design challenges and tradeoffs will be discussed for both high performance platforms as well as mobile platforms. This will be followed by a discussion on power optimization of manycore systems, on-chip communication fabrics, system-level power managment for real-time applications, power and performance modeling of manycore systems and a discussion on physical design challenges. The forum concludes with a panel discussion providing the opportunity for participants to give feedback and ask questions.

Original languageEnglish
Title of host publication2012 IEEE International Solid-State Circuits Conference, ISSCC 2012 - Digest of Technical Papers
Pages508-509
Number of pages2
DOIs
Publication statusPublished - 2012
Event59th IEEE International Solid-State Circuits Conference, ISSCC 2012 - San Francisco, United States
Duration: 19 Feb 201223 Feb 2012
Conference number: 59

Conference

Conference59th IEEE International Solid-State Circuits Conference, ISSCC 2012
Abbreviated titleISSCC 2012
Country/TerritoryUnited States
CitySan Francisco
Period19/02/1223/02/12
Other“Silicon Systems for Sustainability”

Fingerprint

Dive into the research topics of 'F6: Power/performance optimization of many-core processor SoCs'. Together they form a unique fingerprint.

Cite this