Open devreal opened 5 months ago
We have to think more about asynchronous communication handling. We do not want for the user to fence everywhere.
I understand your concerns about the semantics and the MPI standard and it was one of the reasons to move from the KokkosMPI name as I am not sure we can strictly follow MPI.
I think we do not want to require a device-aware MPI implementation. So the code will be less straightforward, with explicit deep_copy
and temporary buffers etc.
Some thoughts I had while browsing through the code:
mpi_assert_allow_overtaking
option in MPI 4.0 (disabling ordering of same-tag messages). Either way, the semantics should be well-defined.