George Bosilca ea3cb1e110 Don't forget to call del_procs. ... This commit was SVN r30430.		2014-01-26 17:26:40 +00:00
..
help-mpi-runtime.txt	Remove tabs for spaces, fix some error messages.	2013-03-01 19:13:06 +00:00
Makefile.am	Fix longstanding issue with our multi-project support. Rather than using	2014-01-07 22:11:15 +00:00
mpiruntime.h	Per RFC add initial support for the MPI 3.0 tools interface.	2013-04-24 15:59:23 +00:00
ompi_cr.c	MCA/base: Add new MCA variable system	2013-03-27 21:09:41 +00:00
ompi_cr.h	Move the RTE framework change into the trunk. With this change, all non-CR	2013-01-27 23:25:10 +00:00
ompi_info_support.c	tools: Add oshmem_info utility	2013-10-12 19:03:32 +00:00
ompi_info_support.h	tools: Add oshmem_info utility	2013-10-12 19:03:32 +00:00
ompi_module_exchange.c	Revert r29917 and replace it with a fix that resolves the thread deadlock while retaining the desired debug info. In an earlier commit, we had changed the modex accordingly:	2013-12-17 03:26:00 +00:00
ompi_module_exchange.h	Move the RTE framework change into the trunk. With this change, all non-CR	2013-01-27 23:25:10 +00:00
ompi_mpi_abort.c	Per this email thread:	2013-12-18 17:57:37 +00:00
ompi_mpi_finalize.c	Don't forget to call del_procs.	2014-01-26 17:26:40 +00:00
ompi_mpi_init.c	remove bml_init call, called from btl add_proc.	2014-01-17 16:52:20 +00:00
ompi_mpi_params.c	For large scale systems, we would like to avoid doing a full modex during MPI_Init so that launch will scale a little better. At the moment, our options are somewhat limited as only a few BTLs don't immediately call modex_recv on all procs during startup. However, for those situations where someone can take advantage of it, add the ability to do a "modex on demand" retrieval of data from remote procs when we launch via mpirun.	2014-01-11 17:36:06 +00:00
ompi_mpi_preconnect.c	MCA/base: Add new MCA variable system	2013-03-27 21:09:41 +00:00
params.h	Since the calls to "PMI get" scale by number of procs (not nodes), it makes more sense to have the MCA param be the cutoff based on number of procs. Also, it occurred to me that this shouldn't impact the nidmap process as that is built and circulated when we launch via mpirun, not during direct launch.	2013-08-22 03:40:26 +00:00