5 Коммитов

Автор	SHA1	Сообщение	Дата
Tim Mattox	4acfbe6554	Unfortunately, the typo's that r22129 tried to fix were not ... as simple as I or Ralph had hoped. This should be the real fix, or very close to it. I can now see both the sensor and rmcast information from ompi_info when configured with --enable-monitoring --enable_multicast This commit was SVN r22131. The following SVN revision numbers were found above: r22129 --> open-mpi/ompi@02ff00dfb5	2009-10-23 02:38:51 +00:00
Ralph Castain	18960a9c5a	Refactor the multicast support so the data type objects can be accessed beyond just the one component ... Ensure that the local node is included in the allocation prior to bootstrap discovery This commit was SVN r22099.	2009-10-14 17:43:40 +00:00
Ralph Castain	84cc847be8	Next phase of auto-wireup using multicast. Enable use of multicast groups to separate comm from different application groups. Have the orted bootstrap message go to a different rml tag so the node can be added to the pool. ... This commit was SVN r22083.	2009-10-10 01:19:56 +00:00
Ralph Castain	1d7ab97c84	Update the multicast framework to allow specification of different message scopes per various RFCs. Redefine the API a little to utilize channel numbers without worrying about the specifics of their addressing ... This commit was SVN r22037.	2009-09-30 14:40:43 +00:00
Ralph Castain	c3f9096fd9	Add a reliable multicast framework, with an initial basic module. This is configured out unless specifically requested via --enable-multicast. ... This commit was SVN r21988.	2009-09-22 00:58:29 +00:00