do I need some additional permissions somewhere?
Wesley (cc'd) can give you access to the private MPI Forum Github repo.
I think there is merit in this suggestion for a nonblocking and persistent versions of MPI_Sendrecv and MPI_Sendrecv_replace.
I’m forwarding this to the point-to-point working group email list so that others have a chance to see it and comment.
Cheers,
Dan.
—
Dr Daniel Holmes PhD
Applications Consultant in HPC Research
d.holmes@epcc.ed.ac.uk
Phone: +44 (0) 131 651 3465
Mobile: +44 (0) 7940 524 088
Address: Room 2.09, Bayes Centre, 47 Potterrow, Central Area, Edinburgh, EH8 9BT
Dr Daniel Holmes PhD
Applications Consultant in HPC Research
d.holmes@epcc.ed.ac.uk
Phone: +44 (0) 131 651 3465
Mobile: +44 (0) 7940 524 088
Address: Room 2.09, Bayes Centre, 47 Potterrow, Central Area, Edinburgh, EH8 9BT
—
The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
—
On 6 Mar 2019, at 16:58, brandongc <notifications@github.com> wrote:
I would like to propose adding a nonblocking sendrecv. This is different from MPI_ISEND + MPI_IRECV + MPI_WAITALL in that 1 fewer request is involved and is far more convenient for developers who wish to convert blocking code to nonblocking. Additionally there are not persistent versions currently.
At a minimum I would like to add:
- MPI_ISENDRECV
- MPI_ISENDRECV_REPLACE
Persistent versions would involve adding:
- MPI_SENDRECV_INIT
- MPI_SENDRECV_REPLACE_INIT
If people think it is a good idea I can to put the relevant text together in a branch. Is there a place for that under https://github.com/mpiwg-p2p? or do I need some additional permissions somewhere?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
