Skip to content

Improve how BTL progress functions are registered #1695

Closed
@jsquyres

Description

@jsquyres

Per #1676 and open-mpi/ompi-release#1174, we probably want to improve how BTL progress functions are invoked. Suggestions:

  1. Separate, low-priority progress functions for advancement of incoming connections.
  2. Don't have R2 always register BTL progress functions -- let BTLs register their own progress functions as they see fit (or not).
  3. Might be better to trigger CM progress threads based on time rather than number of iterations through opal_progress().

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions