1. 1 Calibrating Achievable Design: Technology Extrapolation, the Bookshelf, and Metrics Theme Summary Cong, Dai, Kahng, Keutzer, Maly

2. 2 Mission Enable the understanding of achievable design

3. 3 Motivations u Provide system-level design with predictable implementation u Prove GSRC’s real collaboration, effect on real practice u GSRC has potential critical mass, ability to influence u “Life is short (play hard)” –be mature, efficient -- don’t waste time or effort –standard practices, understandings, backplanes for the field enable researchers, tool providers to focus on core competencies, own value-add u Address productivity gap with each initiative –effective research, effective assessment, effective adoption (Bookshelf) –focusing of effort: distinguish real issues from non-issues (GTX) –optimize the use of tools, not just the tools themselves (Metrics)

4. 4 Vision u GTX –regularly improved, used across academe/industry –expert distributed ownership of modules (scaling, test, cost, …) –useful inferences have aided prioritization of research, tool devel –contains “living ITRS” (e.g., consistent derivation of Table B-1 ORTC’s) u Bookshelf –culture shift to “publication” of implementations; field adopts mature reporting, evaluation/comparison of experimental algorithm research –GSRC’s own backplane/sandbox integrated with industry tools/methods –real force behind development, convergence on data model u Metrics –standard metrics, standard COTS-based infrastructure established –GSRC’s own tools, flows all metricized; EDA vendors see the light –new R&D enabled by availability of design process data repositories u Our partners, colleagues involved and engaged!!!

5. 5 Commitments and Organization u GSRC PIs –Jason Cong 33% –Wayne Dai 100% –Andrew Kahng 100% –Kurt Keutzer 20% –Wojciech Maly 50% u Mindshare / joining in from Constructive Fabrics, Test u Committed participation from partners/sponsors … ? –technology extrapolation calibration data, models –Bookshelf (formulations, formats, underlying data model) –metrics for design artifacts, tools and design processes u Browsing, feedback, proselytizing from everyone … ?

6. 6 GTX: Technology Extrapolation

7. 7 Team Status u GTX Engine and GUI –Mike Oliver (design, implementation) –Andy Caldwell and Igor Markov (design) u GTX Rules –Farinaz Koushanfar, Hua Lu, Dr. Dirk Stroobandt u Theme PIs –Dai: models of block packing –Cong: executable “rules” for BIS/WS interconnect optimization, via Dr. Wangning Long (based on TRIO package) –Keutzer: new student to take over device / scaling module ? –Cheng/Dey/Roy

8. 8 Soft Block Packer (UCSC) u A Result of Soft Block Packing Using Simulated Annealing with Cost Function: Cost = Total Packing Area

9. 9 R d0 driver effective resistance of the input stage G 0 R d driver effective resistance of G linterconnect wire length C L loading capacitance G Input G0G0 l CLCL What is the optimized delay? Do not run TRIO or other optimization tools ! DEM - Delay Estimation Models for Interconnects

10. 10 Some Applications of DEM’s u Layout-driven RTL and physical level floorplanning u Consider interconnect opt. during high / logic level synthesis –Use DEM to predict accurate interconnect delay without really going into layout details –Use accurate interconnect delay to guide synthesis u Interconnect Planning u Ground-truth study -- GTX (Ground Truths/Technology Extrapolation) u …...

11. 11 DEM Library -Delay Estimation Models for Interconnects u Capabilities Delay estimation based on interconnect optimization techniques: –OWS (Optimal Wire Sizing) Critical length for buffer insertion under OWS –SDWS (Simultaneous Driver and Wire Sizing) –BIWS (Buffer Insertion and Wire Sizing) –BISWS (Buffer Insertion, Sizing and Wire Sizing) u Functions: –Tows, Lcrit, Tsdws, Tbiws, Tbisws, ……

12. 12 Wireability Analysis u Observations –a priori WL estimates (e.g., Donath-type) do not take physical metal layers into account (unlimited wiring capacity assumed) –choice of wire pitches at layers independent of considering wire lengths on these layers –effects of vias and repeaters on WL left unstudied u Given: –# layers (or, layer types) –wire pitch at each layer (at each layer type) –estimated wirelength distribution –Which interconnects will be routed on which layer? u Given: –allowed WL intervals for each layer type –How many layers of each type are needed to handle all wires ?

13. 13 Wireability Analysis u Given: –# tier types, wire pitch at each tier type –estimated wirelength distribution –interconnect dimensions and electrical properties –How many layers of each type are needed to accommodate all wires such that the max-length wire at each tier has same delay for all tier types? u Given: –estimated wirelength distribution, and maximal delay –What is the optimum number of tiers, and what are the optimal interconnect dimensions for each tier? u These questions are now addressed in GTX via code rules u Still to do: improved model of vertical interconnect

14. 14 Whitepaper Trail of GTX u “optimum design strategy from manufacturing cost point of view” u “sensitivity analysis of ITRS cycle time projections” u “a self-consistent technology roadmap for semiconductors” u “wireability analysis and interconnect process optimization for multi-terminal nets, repeaters and explicit vertical interconnect” u “impact of 1- and 2-exposure altPSM on speed, density, perf” u “appropriate choice of fault models for XXX” (DSM test)

15. 15 The Bookshelf

16. 16 Use Scenarios u Steering committee solicits submissions –bookshelf supports encyclopedic and unbiased coverage u Researchers volunteer to submit their codes as entries –bookshelf gives additional credit to past work u Industrial affiliates publish benchmarks –publicity to the company and a boost for academic research u Students using bookshelf working on dissertation –bookshelf offers reference and educational help u Reviewers use Bookshelf to evaluate a new paper –bookshelf helps easy evaluation u Researchers compare new algos to what’s in Bookshelf –bookshelf ensures competitiveness

17. 17 Current State u Creation of several “charter” slots –hot areas: hypergraph partitioning, standard-cell placement, single-tree interconnect synthesis, block placement/packing –emphasis on high quality, exemplary behaviors (e.g., source code release) –will meet stated goal for December (3-5 slots instantiated) u Outreach to academic groups and industrial affiliates –advisory role for slot definition u problem statements u format specifications –contribution of reference data, entries –prototype content of file format slots has been distributed u Current infrastructure is Web-accessible tree

18. 18 Open Issues u How to achieve visibility, critical mass ? –support by contributions –support by editorial policies, conference review policies –need publicity and consistent message (N.B.: embedded tutorial at ICCAD99 was dinged) u Integration of the bookshelf –with the development model supported by GSRC –common data models and file formats u Scalability and infrastructure for reuse –not frightening anyone away with excessive requirements u Policy for dealing with restrictions on reuse

19. 19 Sketch of a Slot u Introduction and overview u New Placement Formats u Publicly available instances, solutions and reference performance results u Executable Utilities (converters, generators, statistics browsers, evaluators, constraint verifiers) u Optimizers and other non-trivial executables u Common in-memory representations, parsers and other source codes

20. 20 General Guidelines u Introduction u Motivation and Main Goals u Gotchas u Agreements u Open issues u Availability Status of New Data Formats u Resources u Appendix A. Note to Developers

21. 21 New Common Data Formats u John Lillis at UIC –Single-tree Interconnect Synthesis (.pins,.topo,.target ) –http://www.eecs.uic.edu/~ajaganna/gsrc/new_formats.txt u Patrick Madden at SUNNY Binghamton –Global Routing –http://sol.cs.binghamton.edu/~pmadden/gsrc/gridgraph.html u Wayne Dai at UCSC –Block Packing (.blks,.bconstr,.areapin ) –http://www.cse.ucsc.edu/~huaizhi/bookshelf/bfp1.0 u ABKGroup at UCLA –Standard-cell placement (core formats) (.nodes,.nets,.wts,.scl,.pl ) –http://vlsicad.cs.ucla.edu/GSRC/bookshelf/Slots/Placement –Extensions for partitioning (.blk,.fix,.sol ) –http://vlsicad.cs.ucla.edu/GSRC/bookshelf/Slots/Partitioning

22. 22 Summary of Bookshelf Status u Initial bookshelf slots: u Proselytizing: Tim Cheng at ITC, etc. u Insertion into review processes ? u Active convergence on data formats, tool linkages –UIC, UCLA, SUNY Binghamton, UCSC in initial loop –2 Ph.D. students + outsourcing to interested/engaged researchers –practical driver for efforts toward GSRC-standard data model and API u Standards –standards (build system, platform, software, etc.) near-converged u Commercial backplane –tools (back-end implementation flow) from Synopsys, Cadence –compare against, integrate, mix-and-match with mini-flow above –industry data also sought

23. 23 Metrics

24. 24 Metrics Data Warehouse Tool xmitter Data-Mining Reporting Inter/Intra-net Server Java Applets Web Browsers Wrapper, embedded AI Metrics System Architecture

25. 25 Strategy u Team: Stefanus Mantik (Ph.D. student), OxSigen u Leverage existing infrastructure –OxSigen metrics list, model, prototype servers/reports – standard components (Oracle8i, XML encryption, MSFT UPNP) u Validate definitions of metrics with partners –metrics used by designers, std names, appropriate for tool classes u Develop solutions for basic decisions –protocols for metrics transmittal, retrieval –security, access levels –data integrity (bad data, optimization of transmission, … –consistency of metrics names, semantics between different tools –(identifying the right data, getting it out of tools) –(does tool context contain enough data? (e.g., P&R knows “datapath”?)) –maintenance, evolution of metrics set, schema and APIs

26. 26 First-Year (Milestones) u Sept 1999: transmittal API, Oracle8i install u Oct 1999: DB interface for transmittal, table structures, GSRC-endorsed standards (metrics schema, API), metricize one or two GSRC tools u Nov 1999: completion of transmittal side, initial website for retrieval

27. 27 Summary of Metrics Status u Metrics infrastructure –substantial IP recently obtained from OxSigen LLC (used at Siemens) –Metrics warehouse: data model, schema, API, servlets –Metrics transmitter: applets to write metrics, embeddable in tools –Off-the-shelf standard components: Oracle8i, XML, Java –OxSigen scripts + extensions wrapped around today’s tool logfiles : metricizes the baseline (Synopsys/Cadence) GSRC back-end flow –1 Ph.D. student will do thesis on Metrics in EDA u Need: –buy-in from EDA companies –pull from EDA customers = GSRC sponsors

28. 28 December Show u GSRC Technology Extrapolation system, GTX1.0 –arbitrary tradeoff studies, parameter optimizations –platform-independent engine, GUI; flexible definition/display of studies –param/rule definition: interactive, code/table/ASCII based –accurate models of (1) optimization effects in layers between individual wires/devices and system architecture (UCLA DEM, UCSC soft-block packer); (2) global interconnect resource; etc. –documented, comprehensive; distributed participation –insights on sensitivities, accuracy of existing extrapolations; “new” ones u Bookshelf –publicize, internalize, externalize desired culture/behavior goals –3-5 slots instantiated with entries from multiple investigators –mini-flow built around partitioning / soft-block packing / cell placement / interconnect opt / global routing –evidence of driving force toward data model, tool/flow backplane u Metrics –integration of OxSigen IP, basic transmit/retrieve/report functionality –GSRC proposal of standard Metrics schema and API –GSRC sites running metricized std implementation methodology