2004-08-17 22:24:17 +00:00
|
|
|
#
|
2005-11-05 19:57:48 +00:00
|
|
|
# Copyright (c) 2004-2005 The Trustees of Indiana University and Indiana
|
|
|
|
|
# University Research and Technology
|
|
|
|
|
# Corporation. All rights reserved.
|
|
|
|
|
# Copyright (c) 2004-2005 The University of Tennessee and The University
|
|
|
|
|
# of Tennessee Research Foundation. All rights
|
|
|
|
|
# reserved.
|
2004-11-28 20:09:25 +00:00
|
|
|
# Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
|
|
|
|
|
# University of Stuttgart. All rights reserved.
|
2005-03-24 12:43:37 +00:00
|
|
|
# Copyright (c) 2004-2005 The Regents of the University of California.
|
|
|
|
|
# All rights reserved.
|
2009-06-12 17:52:17 +00:00
|
|
|
# Copyright (c) 2009 Cisco Systems, Inc. All rights reserved.
|
Although we never really thought about it, we made an unconscious assumption in the mapper system - we assumed that the daemons would be placed on nodes in the order that the nodes appear in the allocation. In other words, we assumed that the launch environment would map processes in node order.
Turns out, this isn't necessarily true. The Cray, for example, launches processes in a toroidal pattern, thus causing the daemons to wind up somewhere other than what we thought. Other environments (e.g., slurm) are also capable of such behavior, depending upon the default mapping algorithm they are told to use.
Resolve this problem by making the daemon-to-node assignment in the affected environments when the daemon calls back and tells us what node it is on. Order the nodes in the mapping list so they are in daemon-vpid order as opposed to the order in which they show in the allocation. For environments that don't exhibit this mapping behavior (e.g., rsh), this won't have any impact.
Also, clean up the vm launch procedure a little bit so it more closely aligns with the state machine implementation that is coming, and remove some lingering "slave" code.
This commit was SVN r25551.
2011-11-30 19:58:24 +00:00
|
|
|
# Copyright (c) 2011 Los Alamos National Security, LLC. All rights
|
|
|
|
|
# reserved.
|
2004-11-22 01:38:40 +00:00
|
|
|
# $COPYRIGHT$
|
|
|
|
|
#
|
|
|
|
|
# Additional copyrights may follow
|
|
|
|
|
#
|
2004-08-17 22:24:17 +00:00
|
|
|
# $HEADER$
|
|
|
|
|
#
|
|
|
|
|
|
2012-01-29 10:12:02 +00:00
|
|
|
EXTRA_DIST = base/.windows
|
|
|
|
|
|
2008-06-18 03:15:56 +00:00
|
|
|
headers += \
|
|
|
|
|
base/base.h
|
|
|
|
|
|
|
|
|
|
libmca_rmaps_la_SOURCES += \
|
|
|
|
|
base/rmaps_base_open.c
|
|
|
|
|
|
|
|
|
|
if !ORTE_DISABLE_FULL_SUPPORT
|
|
|
|
|
|
2006-07-11 14:48:31 +00:00
|
|
|
dist_pkgdata_DATA = base/help-orte-rmaps-base.txt
|
2006-07-11 12:15:25 +00:00
|
|
|
|
2005-11-20 01:03:01 +00:00
|
|
|
headers += \
|
2006-09-14 21:29:51 +00:00
|
|
|
base/rmaps_private.h
|
2005-11-20 01:03:01 +00:00
|
|
|
|
|
|
|
|
libmca_rmaps_la_SOURCES += \
|
|
|
|
|
base/rmaps_base_close.c \
|
2008-06-18 03:15:56 +00:00
|
|
|
base/rmaps_base_select.c \
|
2006-09-14 21:29:51 +00:00
|
|
|
base/rmaps_base_map_job.c \
|
2009-06-12 17:52:17 +00:00
|
|
|
base/rmaps_base_support_fns.c \
|
At long last, the fabled revision to the affinity system has arrived. A more detailed explanation of how this all works will be presented here:
https://svn.open-mpi.org/trac/ompi/wiki/ProcessPlacement
The wiki page is incomplete at the moment, but I hope to complete it over the next few days. I will provide updates on the devel list. As the wiki page states, the default and most commonly used options remain unchanged (except as noted below). New, esoteric and complex options have been added, but unless you are a true masochist, you are unlikely to use many of them beyond perhaps an initial curiosity-motivated experimentation.
In a nutshell, this commit revamps the map/rank/bind procedure to take into account topology info on the compute nodes. I have, for the most part, preserved the default behaviors, with three notable exceptions:
1. I have at long last bowed my head in submission to the system admin's of managed clusters. For years, they have complained about our default of allowing users to oversubscribe nodes - i.e., to run more processes on a node than allocated slots. Accordingly, I have modified the default behavior: if you are running off of hostfile/dash-host allocated nodes, then the default is to allow oversubscription. If you are running off of RM-allocated nodes, then the default is to NOT allow oversubscription. Flags to override these behaviors are provided, so this only affects the default behavior.
2. both cpus/rank and stride have been removed. The latter was demanded by those who didn't understand the purpose behind it - and I agreed as the users who requested it are no longer using it. The former was removed temporarily pending implementation.
3. vm launch is now the sole method for starting OMPI. It was just too darned hard to maintain multiple launch procedures - maybe someday, provided someone can demonstrate a reason to do so.
As Jeff stated, it is impossible to fully test a change of this size. I have tested it on Linux and Mac, covering all the default and simple options, singletons, and comm_spawn. That said, I'm sure others will find problems, so I'll be watching MTT results until this stabilizes.
This commit was SVN r25476.
2011-11-15 03:40:11 +00:00
|
|
|
base/rmaps_base_ranking.c \
|
|
|
|
|
base/rmaps_base_print_fns.c
|
|
|
|
|
|
|
|
|
|
if OPAL_HAVE_HWLOC
|
|
|
|
|
libmca_rmaps_la_SOURCES += \
|
|
|
|
|
base/rmaps_base_binding.c
|
|
|
|
|
endif
|
|
|
|
|
|
2008-06-18 03:15:56 +00:00
|
|
|
endif
|