-
Notifications
You must be signed in to change notification settings - Fork 908
Closed as not planned
Description
Originally taken from the "to-do" section in the Open MPI docs:
- Update mpirun man page #11730
- Eliminiated all -foo options
- Modernized some of the examples
- Much more work needs to be done to update it for all the PRTE changes since Open MPI v4.1.x.
- Document new breakpoint functionality #11731
- Add that we do support “single dash”
mpirun
options, but we don’t want people to do that. - We need to document how to use MPI_Comm_join and MPI_Publish_name + MPI_Comm_accept / MPI_Lookup_name + MPI_Comm_connect after PRRTE changes. #11732
- Add a section about debugging and removal of MPIR #11733
- ORTE -> PRRTE changes for users need to be documented, users educated #7668 (ORTE –> PRRTE user-visible changes)
- Add docs about mpirun launch vs. direct launch. #11734
- Investigate and document current behavior of "aggressive" mode #11735
- This is an old link to section 10.8.21 -- it may or may not be correct https://ompi–8329.org.readthedocs.build/en/8329/faq/running-mpi-apps.html
- Is "aggressive" mode really determined by the slot count provided by PRRTE? Or is it determined by a query to hwloc with a reference to the number of processes per node. It just surprises me that this part of OMPI is controlled by PRRTE instead of something more generic that might work with, say, Slurm direct launch via
srun
.
- From Ralph's comment on singleton mode with v4.x fails when MCA binding policy is "numa" on AMD hardware #11097: