Hui Zhou
Hui Zhou
> `ImportError: /usr/local/lib/libmpi_abi.so.0: undefined symbol: MPIX_Async_get_state` I try not to expose MPIX functions to the ABI build. Is this an issue with mpi4py? > `../mpich/src/util/mpir_async_things.c:35:13: error: implicit declaration of function...
test:mpich/ch4/ofi ✔️
test:mpich/warnings/auto
Test on my local computer: ``` $ MPIR_CVAR_DEBUG_SUMMARY=1 mpirun -hosts 172.17.0.1 -n 1 ./cpi ==== Various sizes and limits ==== sizeof(MPIDI_per_vci_t): 192 Required minimum FI_VERSION: 0, current version: 1000f provider:...
test:mpich/ch3/most test:mpich/ch4/most
> what value did you set PMI_HOSTNAME to ? To the IP address of your local host. Hydra (mpiexec) in this PR will set it automatically.
Tests such as the pingping tests may flood the receiver with unexpected messages. This is intrinsically a performance issue. No design can deal with unlimited unexpected messages. So I think...
> Is the goal to preserve the MPI semantics of the existing MPI calls such that they guarantee local or remote completion on return to the calling context (which is,...
> 1. The caller make guarantees about the state of a buffer before calling MPI with a buffer, in the case of IRecv that the buffer is ready for MPI...
> My understanding was that Send, Recv, and Wait called on stream communicators with an associated GPU stream (even when not called through the _enqueue interface) resulted in enqueuing operations;...