How Much Does Regularity Help FPGA Placement?

Hongxin Kong, Lang Feng, Chunhua Deng, Bo Yuan, Jiang Hu

Research output: Chapter in Book/Report/Conference proceedingConference contribution

1 Scopus citations

Abstract

Placement plays a key role in determining FPGA circuit characteristics. Meanwhile, its long computation time is an important factor that makes the flexibility of FPGA computing much less competitive than software compiling. One observation is that there is an increasing need for designs with regularity. A particular example is systolic array-based neural network circuit design. In this work, FPGA placement exploiting design regularity is studied. For neural network designs with systolic arrays, our proposed regularity-Aware approach achieves 2X to 28X speed up versus Versatile Place and Route (VPR) with limited circuit performance loss. At the same time, its solution quality is almost perfectly correlated with VPR and thus renders its role for early prototyping.

Original languageEnglish (US)
Title of host publicationProceedings - 2020 International Conference on Field-Programmable Technology, ICFPT 2020
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages76-84
Number of pages9
ISBN (Electronic)9780738105185
DOIs
StatePublished - Dec 2020
Externally publishedYes
Event2020 International Conference on Field-Programmable Technology, ICFPT 2020 - Maui, United States
Duration: Dec 7 2020Dec 8 2020

Publication series

NameProceedings - 2020 International Conference on Field-Programmable Technology, ICFPT 2020

Conference

Conference2020 International Conference on Field-Programmable Technology, ICFPT 2020
Country/TerritoryUnited States
CityMaui
Period12/7/2012/8/20

All Science Journal Classification (ASJC) codes

  • Artificial Intelligence
  • Computational Theory and Mathematics
  • Computer Networks and Communications
  • Hardware and Architecture

Fingerprint

Dive into the research topics of 'How Much Does Regularity Help FPGA Placement?'. Together they form a unique fingerprint.

Cite this