-
Notifications
You must be signed in to change notification settings - Fork 900
Added an initial implementation of partitioned communication. #8044
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Can one of the admins verify this patch? |
Signed-off-by: Matthew G. F. Dosanjh <[email protected]>
ok to test |
Also added @mdosanjh to the Open MPI github org. |
@mdosanjh We should probably work on getting the non-blocking window creation done if it isn't already underway. That would address the caveat. |
@hjelmn Agreed; I haven't started looking at that yet but it is on my todo list. There's also an MPI_Comm_create_group in the init calls that also prevents a non-blocking implementation (this is to limit the window to the two processes involved and ensure the tags match). I'm wondering if it is feasible to create a non-blocking MPI_Win_create that uses a group to only include a subset of the processes (eliminating the need for MPI_Comm_create_group). |
@jsquyres I got the following error message: This doesn't appear to be an issue with my code (though I could be wrong) is there a way to re-run the tests? |
bot:aws:retest |
bot:retest |
The IBM CI (PGI) build failed! Please review the log, linked below. Gist: https://gist.github.com/bd05eb727e830d4a91645c5f35ee6ff6 |
The PGI failure log is super long, but it's there if you download it. Here is the error:
The file is super long because of piles and piles these warnings (@awlauria do we have a PGI cleanup PR to address this?):
|
#8444 should clean up that PGI warning. I just need to push myself to finish it. I'll try to rebase this week |
This is an initial implementation of partitioned communication, adding the part mca component and 'rma module' for the initial back end implementation (this initial implementation uses the MPI RMA interface).
There is one notable caveat to this implementation; that both MPI_Psend_init and MPI_Precv_init are blocking, which is not compliant with the upcoming MPI-4 specification.
.