Galen Shipman 18d1d3b408 Add ORTE ALPS support (Cray XT CNL) ...

This commit was SVN r17482.

2008-02-17 19:29:06 +00:00

..

data_type_support

reapply r15517 and r15520, which were removed in r15527 so that I could get

2007-07-20 02:34:29 +00:00

proxy

A number of improvements / changes to the RML/OOB layers:

2007-07-20 01:34:02 +00:00

base.h

Add timing tests for the TM ras

2006-11-06 18:41:22 +00:00

Makefile.am

Restore the paffinity capability, along with all the required logic to ensure we "do the right thing" when the user gives us inaccurate information about the number of slots on a remote node.

2006-12-06 15:59:34 +00:00

ras_base_alloc.c

Here is the major MAD-cure commit. I have written plenty about it, so I refer you here to those messages for a description of everything that was done.

2006-09-14 21:29:51 +00:00

ras_base_allocate.c

Back out some prior commits. These commits fixed bproc so it would run, but broke several other things (singleton comm_spawn and hostfile operations have been identified so far). Since bproc is the culprit here, let's leave bproc broken for now - I'll work on a fix for that environment that doesn't impact everythig else.

2006-11-22 13:30:21 +00:00

ras_base_close.c

Continue bringing comm_spawn back online. Ensure all RM frameworks post their HNP receives. Fix the rmgr proxy component.

2006-10-02 00:46:31 +00:00

ras_base_find_available.c

Continue bringing comm_spawn back online. Ensure all RM frameworks post their HNP receives. Fix the rmgr proxy component.

2006-10-02 00:46:31 +00:00

ras_base_no_ops.c

reapply r15517 and r15520, which were removed in r15527 so that I could get

2007-07-20 02:34:29 +00:00

ras_base_node.c

reapply r15517 and r15520, which were removed in r15527 so that I could get

2007-07-20 02:34:29 +00:00

ras_base_open.c

Fix invalid MCA 'base' names so they appear in ompi_info.

2007-08-18 03:05:45 +00:00

ras_base_receive.c

Bring over the update to terminate orteds that are generated by a dynamic spawn such as comm_spawn. This introduces the concept of a job "family" - i.e., jobs that have a parent/child relationship. Comm_spawn'ed jobs have a parent (the one that spawned them). We track that relationship throughout the lineage - i.e., if a comm_spawned job in turn calls comm_spawn, then it has a parent (the one that spawned it) and a "root" job (the original job that started things).

2006-11-14 19:34:59 +00:00

ras_base_support_fns.c

Add ORTE ALPS support (Cray XT CNL)

2008-02-17 19:29:06 +00:00

ras_private.h

Add ORTE ALPS support (Cray XT CNL)

2008-02-17 19:29:06 +00:00