1 / 5

OFI SW – Progress Revisited

OFI SW – Progress Revisited. Sean Hefty - Intel Corporation. Recap. Ability of the underlying implementation to complete processing of an asynchronous request Need to consider ALL asynchronous requests Connections, address resolution, data transfers, event processing, completions, etc.

wayne
Télécharger la présentation

OFI SW – Progress Revisited

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. OFI SW – ProgressRevisited Sean Hefty - Intel Corporation

  2. Recap • Ability of the underlying implementation to complete processing of an asynchronous request • Need to consider ALL asynchronous requests • Connections, address resolution, data transfers, event processing, completions, etc. • HW/SW mix All(?) current solutions require significant software components www.openfabrics.org

  3. Proposal • Support two progress models • Automatic and implicit (name?) • Identify operations as belong to one of two progress domains • Data or control www.openfabrics.org

  4. Proposal • Implicit progress • Occurs when reading or waiting on EQ(s) • Application can use separate EQs for control and data • Progress limited to endpoints associated with selected EQ(s) • App can request automatic progress • E.g. app wants to wait on native wait object • Implies provider allocated threading www.openfabrics.org

  5. Implementation • Progress attributes added to fi_info • Optional input hints • If not specified, provider reports optimal model • Event queue operations • Read and wait – single EQ • Domain operations • Read and wait – multiple EQs www.openfabrics.org

More Related