Manjunath Gorentla Venkata

Did we converge on this ? If not, let's discuss this in the WG tomorrow.

@alex--m As we discussed in the WG, the change-set is beyond the scope of the UCC community. Can you please identify the commits/change-set that needs to be reviewed by the...

From the spec: **_"Invocation semantics: The ucc_team_create_post is a nonblocking collective operation, in which the partic- ipants are determined by the user-provided OOB collective operation. Overlapping of multiple ucc_team_←􏰀 create_post...

Does this address some of the questions?

1) For context creation, we don’t want to place this restriction. Because you want to support the use case where you want to create resource per thread and that is...

> 1. I think we still should prohibit concurrent context creations from multiple threads. The user should create contexts and then give them to different threads this is fine, but...

> 2\. How will ucc implement anything internally w/o having means of communication and any info about the "world". Do you imply PMIx integration there ? Yes.

> * Is it allowed to call ucc_collective_finalize(request_1) and ucc_collective_init/post(request_2) concurrently from 2 different threads on the SAME team ? Ie, concurrent calls to collective_init/post and finalize Since init and...

> * Is it allowed to call ucc_context_progress(ctx) in 1 thread and ucc_team_create/destroy from the same process in another thread? Since context is a local entity, I would yes. To...

@alex--m Please feel free to add details. We can use this as a placeholder for this discussion.