1 / 16

Data Reorganization Interface DRI Overview

2. Outline. DRI specification highlightsDesign/application spaceFeatures in DRI 1.02-D FFT Example*Journal of development (features discussed, but not included in DRI 1.0)DRI forum statusCurrent/future value of DRI to HPEC. * Thanks to Steve Paavola of Sky Computers for contributing to the 2-D

lapis
Télécharger la présentation

Data Reorganization Interface DRI Overview

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. Data Reorganization Interface (DRI) Overview Kenneth Cain Jr., Mercury Computer Systems, Inc. Anthony Skjellum, MPI Software Technology On behalf of the Data Reorganization Forum http://www.data-re.org

    2. 2 Outline DRI specification highlights Design/application space Features in DRI 1.0 2-D FFT Example* Journal of development (features discussed, but not included in DRI 1.0) DRI forum status Current/future value of DRI to HPEC

    3. 3 Design/Application Space

    4. 4 DRI Important Objects

    5. 5 DRI Parallel Mapping

    6. 6 DRI Communication Setup

    7. 7 DRI Parallel Communication

    8. 8 All DRI Objects

    9. 9 DRI In-Place Processing

    10. 10 DRI 2-D FFT Example (1/2)

    11. 11 DRI 2-D FFT Example (2/2)

    12. 12 Journal of Development Topics discussed, but not in DRI 1.0 Piecemeal data production/consumption User-allocated memory Generalized buffer sharing Split data types (e.g., complex, RGB, ) Interoperation with VSIPL Dynamic Transfer sizes (e.g., mode change support) Buffer sizes (lower memory impact for multi-buffering) Process sets: pick process set pair at transfer-time Non-CPU (device) endpoints To address these issues, vendors/users Develop desired extensions (necessarily non-portable) Use experience to focus requirements for future standardization (if appropriate)

    13. 13 DRI Forum Status Future Gather feedback about DRI 1.0 evaluation/use Further specification TBD based on community interest See web page/email list for latest info. Web: http://www.data-re.org Email list: data-reorg@data-re.org

    14. 14 DRI Value to HPEC DRI current value to HPEC community: Implementable with high performance Packages often independently developed data flow features High level of abstraction Reduce source lines of code dedicated to data flow Reduce development time associated with data flow DRI future value to HPEC community: Common framework/terminology in which to focus communitys requirements DRI 1.0 journal of development provides good starting list of expanded features

    15. 15 Recommendations Implement DRI Evaluate/use DRI Inquire with HW/SW vendors about availability Evaluate implementations, provide feedback Focus application requirements Identify what DRI (and other middlewares in this space) must provide Provide feedback to DRI, other HPEC forums Innovate with DRI Develop reference implementations Consider enhancements C++ bindings Integration with processing middleware

    16. 16 Expectations DRI will be an add-on library that works with MPI-1 DRI will be optimized by some library developers to be fast Both a reference implementation and optimized versions are underway Vendor-specific DRI versions that go with their own message passing will also be offered (e.g., Mercury PAS)

More Related