Skip to content

Conversation

@Matthew-Whitlock
Copy link
Contributor

Without a way to revoke the subcomms created by the coll modules, processes can get stuck waiting on sub-operations of a collective on a revoked communicator.
I chose to put the top-level coll_revoke_local into the comm's c_coll object as a function pointer, but that's only to maintain the same programming pattern as the other functions. The top-level function is static, and calls coll_revoke_local on the comm for each of it's active modules.

@Matthew-Whitlock
Copy link
Contributor Author

I don't think this check failure is related to me

Signed-off-by: Matthew Whitlock <mwhitlo@sandia.gov>
Signed-off-by: Matthew Whitlock <mwhitlo@sandia.gov>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

1 participant