13227e36ab
Fix the problem observed by multiple people that comm_spawned children were (once again) being mapped onto the same nodes as their parents. This was caused by going through the RAS a second time, thus overwriting the mapper's bookkeeping that told RMAPS where it had left off. To solve this - and to continue moving forward on the ORTE development - we introduce the concept of attributes to control the behavior of the RM frameworks. I defined the attributes and a list of attributes as new ORTE data types to make it easier for people to pass them around (since they are now fundamental to the system, and therefore we will be packing and unpacking them frequently). Thus, all the functions to manipulate attributes can be implemented and debugged in one place. I used those capabilities in two places: 1. Added an attribute list to the rmgr.spawn interface. 2. Added an attribute list to the ras.allocate interface. At the moment, the only attribute I modified the various RAS components to recognize is the USE_PARENT_ALLOCATION one (as defined in rmgr_types.h). So the RAS components now know how to reuse an allocation. I have debugged this under rsh, but it now needs to be tested on a wider set of platforms. This commit was SVN r12138. |
||
---|---|---|
.. | ||
data_type_support | ||
base.h | ||
help-rmgr-base.txt | ||
Makefile.am | ||
rmgr_base_attribute_fns.c | ||
rmgr_base_check_context.c | ||
rmgr_base_close.c | ||
rmgr_base_con_discon.c | ||
rmgr_base_context.c | ||
rmgr_base_open.c | ||
rmgr_base_receive.c | ||
rmgr_base_select.c | ||
rmgr_base_stage_gate.c | ||
rmgr_base_stubs.c | ||
rmgr_base_vpid_support_fns.c | ||
rmgr_private.h |