Ralph Castain bc7cc09749 After a lot of pain, I've managed to resolve the problem of conflicting mapping directives caused by mismatched MCA params - i.e., where someone has one variant of an MCA param (e.g., rmaps_base_mapping_policy) in their default MCA param file, and then specifies another variant (e.g., --npernode) on the command line. I can't fully resolve the problem as there is no way to know precisely what the user meant - we can only guess which param was really intended since the MCA param system ... can't apply its normal precedence rules. So...print a big "deprecated" warning for the old params and error out if a conflict is detected. I know that isn't what people really wanted, but it's the best we can do. If only the old style param is given, then process it after the warning. Extend the current map-by param to add support for ppr and cpus-per-proc, adding the latter to the list of allowed modifiers using "pe=n" for processing elements/proc. Thus, you can map-by socket:pe=2,oversubscribe to map by socket, binding 2 processing elements/process, with oversubscription allowed. Or you can map-by ppr:2:socket:pe=4 to map two processes to every socket in the allocation, binding each process to 4 processing elements. For those wondering, a processing element is defined as a hwthread if --use-hwthreads-as-cpus is given, or else as a core. Refs trac:4117 This commit was SVN r30620. The following Trac tickets were found above: Ticket 4117 --> https://svn.open-mpi.org/trac/ompi/ticket/4117		2014-02-07 21:25:40 +00:00
..
etc	Backing out the Open SHMEM project	2013-02-12 17:45:27 +00:00
include	Fix longstanding issue with our multi-project support. Rather than using	2014-01-07 22:11:15 +00:00
mca	After a lot of pain, I've managed to resolve the problem of conflicting mapping directives caused by mismatched MCA params - i.e., where someone has one variant of an MCA param (e.g., rmaps_base_mapping_policy) in their default MCA param file, and then specifies another variant (e.g., --npernode) on the command line. I can't fully resolve the problem as there is no way to know precisely what the user meant - we can only guess which param was really intended since the MCA param system	2014-02-07 21:25:40 +00:00
orted	Use unique collective ids for the checkpoint/restart code	2014-02-04 14:03:05 +00:00
runtime	Use unique collective ids for the checkpoint/restart code	2014-02-04 14:03:05 +00:00
test	Add a variant of opal_init/finalize for running unit tests	2014-01-30 11:14:36 +00:00
tools	After a lot of pain, I've managed to resolve the problem of conflicting mapping directives caused by mismatched MCA params - i.e., where someone has one variant of an MCA param (e.g., rmaps_base_mapping_policy) in their default MCA param file, and then specifies another variant (e.g., --npernode) on the command line. I can't fully resolve the problem as there is no way to know precisely what the user meant - we can only guess which param was really intended since the MCA param system	2014-02-07 21:25:40 +00:00
util	Use unique collective ids for the checkpoint/restart code	2014-02-04 14:03:05 +00:00
Doxyfile	Fix the broken Doxyfile so people can generate what little code base documentation we have :-)	2006-04-13 12:52:17 +00:00
Makefile.am	Fix longstanding issue with our multi-project support. Rather than using	2014-01-07 22:11:15 +00:00