Hui Zhou
Hui Zhou
test:mpich/ch4/ofi test:mpich/custom netmod: ch4:ofi env: MPIR_CVAR_CH4_OFI_ENABLE_DATA=0
test:mpich/spellcheck
test:mpich/ch3/most test:mpich/ch4/most test:mpich/custom netmod: ch4:ucx env: with_ucx_spawn=1
test:mpich/ch3/most
@raffenet I enabled ucx spawn tests in jenkins-scripts. You may need to add the exceptions back for stable release tests.
We are currently stuck with the MPICH ABI which defines `MPI_MAX_PORT_NAME` to `256`. A ucx address will not fit in `256`, thus `MPI_Open_port` will fail with ucx + the current...
How would `MPIX_MAX_PORT_NAME` help? By standard, we are required to assume the name buffer in `MPID_Open_port` is bound by `MPI_MAX_PORT_NAME` missing info hint.
For users, it is always safe to allocate a name buffer that is larger than `MPI_MAX_OPEN_PORT`, there is no upper bound. An implementation will never fill the buffer more than...
Yeah, sounds good, assuming the newer generated config.guess will work with older automake (as it should be).
Moving forward, the standardized way of control and query GPU support is via `mpi_memory_alloc_kinds` info hints. Ref. https://github.com/mpi-forum/mpi-issues/issues/580 cc @raffenet