George Bosilca 337f78a4a8 Restrict the port range for the OOB and the BTL. Each protocols (v4 and v6) ...

has his own range which is defined by a min value and a range. By default
there is no limitation on the port range, which is exactly the same
behavior as before.

This commit was SVN r16584.

2007-10-26 16:36:51 +00:00

..

errmgr

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

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

filem

Change some default MCA parameters:

2007-10-15 15:21:17 +00:00

gpr

These changes were mostly captured in a prior RFC (except for #2 below) and are aimed specifically at improving startup performance and setting up the remaining modifications described in that RFC.

2007-10-05 19:48:23 +00:00

grpcomm

Fix a bug in the way we handled buffer releases and the conditioned wait that held us in the xcast until completed.

2007-10-19 01:17:01 +00:00

iof

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

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

ns

Squeeeeeeze the launch message. This is the message sent to the daemons that provides all the data required for launching their local procs. In reorganizing the ODLS framework, I discovered that we were sending a significant amount of unnecessary and repeated data. This commit resolves this by:

2007-10-11 15:57:26 +00:00

odls

The processor affinity must be set on a per-process basis, not per-app-context.

2007-10-23 20:46:16 +00:00

oob

Restrict the port range for the OOB and the BTL. Each protocols (v4 and v6)

2007-10-26 16:36:51 +00:00

pls

When we can detect that a daemon has failed, then we would like to terminate the system without having it lock up. The "hang" is currently caused by the system attempting to send messages to the daemons (specifically, ordering them to kill their local procs and then terminate). Unfortunately, without some idea of which daemon has died, the system hangs while attempting to send a message to someone who is no longer alive.

2007-10-15 18:00:30 +00:00

ras

Squeeeeeeze the launch message. This is the message sent to the daemons that provides all the data required for launching their local procs. In reorganizing the ODLS framework, I discovered that we were sending a significant amount of unnecessary and repeated data. This commit resolves this by:

2007-10-11 15:57:26 +00:00

rds

These changes were mostly captured in a prior RFC (except for #2 below) and are aimed specifically at improving startup performance and setting up the remaining modifications described in that RFC.

2007-10-05 19:48:23 +00:00

rmaps

* Use new BEGIN_C_DECLS / END_C_DECLS convention

2007-10-26 13:40:38 +00:00

rmgr

These changes were mostly captured in a prior RFC (except for #2 below) and are aimed specifically at improving startup performance and setting up the remaining modifications described in that RFC.

2007-10-05 19:48:23 +00:00

rml

The header is at the address of the buffer pointed to by the iov, not

2007-10-19 12:40:14 +00:00

routed

When in the unity message routing mode, we have to update the RML contact info in the parent procs so that they know how to talk to the children. Ideally, this would be done in the MPI layer since that layer knows which procs are actively involved in the comm_spawn. However, it isn't being done there, which causes comm_spawn to fail, so do it explicitly in the RTE.

2007-10-16 16:09:41 +00:00

schema

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

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

sds

Squeeeeeeze the launch message. This is the message sent to the daemons that provides all the data required for launching their local procs. In reorganizing the ODLS framework, I discovered that we were sending a significant amount of unnecessary and repeated data. This commit resolves this by:

2007-10-11 15:57:26 +00:00

smr

revert my stupidity..

2007-10-09 19:01:20 +00:00

snapc

Move in some accumulated small features and minor bug fixes for C/R support.

2007-10-17 13:47:36 +00:00