-
Notifications
You must be signed in to change notification settings - Fork 103
05 06 2020
Manjunath Gorentla Venkata edited this page Jul 30, 2020
·
1 revision
- Manjunath Gorentla Venkata
- Gil Bloch
- Sergey Lebedev
- Alex Margolin
- Valentin Petrov
- Geoffroy Vallee
- James S Dinan
- Akshay Venkatesh
- Ravi, Naveen
Topics to be discussed at the meeting is here: https://github.com/openucx/ucx/wiki/UCC-Virtual-F2F-Meeting-Information
Goals of Component Architecture
- Support different implementations of collective operations
- XCCL, UCG, SHARP, open-source, proprietary
- Ability to support different implementations of collective algorithms
- Abstract p2p communication, memory management, topology, and service libraries
Framework: Framework is a coarse-grained abstraction of the functionality. Enables building of functionality combining different implementations
- What should be a framework? Collectives, p2p communication, services?
Component: A component is a fine-grained abstraction of the functionality.
- What should be a component? An instance of collective implementation, p2p communication, multicast communication?
Component or Framework?
- p2p abstraction
- memory registration
- caching (rcache)
- topology management
- UCS (services)
Component architecture discussion to be continued
- UCC Virtual F2F - (May 11-13, 17-18)