Skip to content

03 11 2020

Jump to bottom
Manjunath Gorentla Venkata edited this page Jul 30, 2020 · 1 revision

Participants:

  • Mikhail (Mellanox)
  • Dmitry Gladkov (Mellanox)
  • Evgeny Leksikov (Mellanox)
  • Gil Bloch (Mellanox)
  • Manjunath Gorentla (Mellanox)
  • Naveen (HPE/Cray)
  • Devendar Bureddy (Mellanox)
  • Sergey Obolomov (Mellanox)
  • Sergey Lebdev (Mellanox)
  • Valentin Petrov (Mellanox)
  • Pavel Shamis (Arm)
  • Alex Margolin (Huawei)
  • Akshay (NVIDIA)

Agenda

  • Announcements
  • Library Initialization
  • Component architecture

Project name: UCC

  • No major conflicts
  • Conflicts with upstream have not been discovered, yet
  • There are some minor conflicts with the acronym but does not seem to be a major concern

CLA

  • No conclusion yet. But, moving towards the direction where if you have signed a CLA for UCX and also a UCF member, you don’t have to sign a new CLA.

The patch to conditionally build an experimental UCG submodule

  • Alex has a wiki page providing an overview of the build process and usage

UCC F2F

  • With the situation around COVID-19, it seems prudent to have a virtual f2f rather than a physical meeting. The virtual f2f to span over a week (Mon-Fri) and four hours of meeting time each day.
  • This is not necessarily the same as f2f from a productivity perspective, but we can revisit the idea of physical f2f as things calm down.
  • Send out some options for April (mid to last week) to choose the most convenient time frame for the majority (AI: Manju)
  • Logistics - Inclination to use BlueJeans
  • Time slot: TBD based on the potential participants.
  • Send an invite to potential participants who are not necessarily regular attendees.

WG meeting to move to weekly cadence.

  • Send out a poll for choosing appropriate time (AI: Manju)

Library initialization

  • Discussion from the previously distributed slides
  • Don’t support experimental API and instead use the library versioning approach (borrow the idea from RDMA Core and UCX is moving towards that direction)
  • Thread models - Use two thread models (UCC_THREAD_MULTIPLE or UCC_THREAD_SINGLE) for now.
  • Discussion about library usage models (to be continued in the next meeting)

Next Meeting:

March 18 or 19 to be based on the poll

Potential agenda for the next meeting

  1. Library initialization
  2. Resource abstraction
  3. Component architecture
  4. Multi-faceted API or single API?
Clone this wiki locally