1 / 10

RAMP Sharing (Playing well with others)

RAMP Sharing (Playing well with others).

gareth
Download Presentation

RAMP Sharing (Playing well with others)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RAMP Sharing (Playing well with others) John Davis, Christos Kozyrakis, Chuck Thacker, Takefumi Miyoshi, Shinya Takamaeda, Phillip Jones, TayoOguntebi, Jared Casper, Andrew Putnam, Michael Papamichael, Eric Chung, RodricRabbah, Manuel Saldana, Hari Angepat, Hong An, AngshumanParashar, David Penry, Kevin W. Rudd, Ralph Wittig

  2. Sharing in RAMP • Who? • Content producers and consumers • What can we share? • Low to high level components • Where do we get/put the shared components? • How do we share? • Why? • When?

  3. System/Platform

  4. Sharing models Top down Bottom up Smaller components e.g., interfaces, firmware, controllers Self-encapsulated, easier to understand, faster path to reuse Easier to reuse in contexts that are not simulation-inclined • Larger chunks of infrastructure e.g., ProtoFlex • An example of application level sharing • Useful if application mostly fits reusable scenario (e.g., processor simulation): can tweak and tailor • May tie you to other subcomponents, harder to reuse but certainly can be mined

  5. Sharing dimensions • Many RAMP projects: universities, students, industry, purposes • Dimensions: platforms, application domains (e.g., type of simulation)

  6. Useful Components to Share • Communications models: • scalar operands, cache line transfers, dmas, notifications (control) • What goes in the FPGA: • caches, memory, pipelines • Software side in CPU: • fifo queues, mpi, stmc • Application level: • Not clear what goes there • Missing features: • configuration, reconfiguration

  7. Using tools • Tools are good • Useful tools are maintained by individuals with “skin in the game” • Harder to adopt tools if grad students, once they graduate, abandon platform • Tools should be well documented

  8. Sharing with transparency • Be upfront about status of component being released • State assumptions and dependencies clearly

  9. Centralized repository for sharing • Someone needs to do this • Consolidate repositories, packages, etc. • Mailing lists, forums, wiki • What RAMP technologies are mature enough for sharing

More Related