S
Salil V. Wadhavkar
Researcher at North Carolina State University
Publications - 5
Citations - 184
Salil V. Wadhavkar is an academic researcher from North Carolina State University. The author has contributed to research in topics: Multi-core processor & Microarchitecture. The author has an hindex of 3, co-authored 5 publications receiving 183 citations. Previous affiliations of Salil V. Wadhavkar include Qualcomm.
Papers
More filters
Proceedings ArticleDOI
FabScalar: composing synthesizable RTL designs of arbitrary cores within a canonical superscalar template
Niket K. Choudhary,Salil V. Wadhavkar,Tanmay A. Shah,Hiran Mayukh,Jayneel Gandhi,Brandon H. Dwiel,Sandeep Navada,Hashem Hashemi Najaf-abadi,Eric Rotenberg +8 more
TL;DR: From this idea, a toolset is developed, called FabScalar, for automatically composing the synthesizable register-transfer-level (RTL) designs of arbitrary cores within a canonical superscalar template, which defines canonical pipeline stages and interfaces among them.
Journal ArticleDOI
FabScalar: Automating Superscalar Core Design
Niket K. Choudhary,Salil V. Wadhavkar,Tanmay A. Shah,Hiran Mayukh,Jayneel Gandhi,Brandon H. Dwiel,Sandeep Navada,Hashem Hashemi Najaf-abadi,Eric Rotenberg +8 more
TL;DR: FabScalar aims to automate superscalar core design, opening up processor design to microarchitectural diversity and its many opportunities.
Proceedings ArticleDOI
A unified view of non-monotonic core selection and application steering in heterogeneous chip multiprocessors
TL;DR: This work considers HCMPs comprised of non-monotonic core types where each core type is performance-optimized to different instruction-level behavior and hence cannot be ranked - different program phases achieve their highest performance on different cores.
Architecting a workload-agnostic heterogeneous multi-core processor
TL;DR: This dissertation addresses the question of choosing the cores in a heterogeneous multi-core in a workload-agnostic manner, and demonstrates potential pitfalls of customization by showing that multi-cores tuned to a subset of the actual workload may perform poorly on the entire workload.