Below a list of stuff that I've got by running mpi4py testsuite. Never
reported them before just because some of them are not actually
errors, but anyway, I want to raise the discussion.
- Likely bugs (regarding my interpretation of the MPI standard)
1) When passing MPI_REQUEST_NULL, MPI_Request_
This is a pretty good suggestion; I think it could be useful to what we're
trying to do with STCI, but I can see that it could be generally useful to
others as well. As long as nobody objects on the grounds that this is too
much to put into a single RFC, I can work towards the goal of incorporatin
Sounds reasonable to me - but again, let's commit it when we do the
1.4 branch so maintaining 1.3 doesn't become impossible.
On Feb 10, 2009, at 2:38 PM, George Bosilca wrote:
These changes look fine to me. However, I would like to amend this
proposal to include the splitting of the config
Hello guys,
I'm running some experimental tcp btl which implements rdma GET method and
advertises it in its flags of the btl API.
The btl`s send() method returns rc=1 to select fast path for PML. (this
optimization was added in revision 18551 in v1.3)
It seems that in PML/ob1, mca_pml_ob1_send_re
