This release candidate is pretty identical to rc2 - only changes were to
correct some minor warnings and prep for final release (update NEWS, README,
and VERSION).
Please give it a whirl so we can get this out!
Ralph
Dear all,
In the past I have used OpenMPI to develop some (simple) applications.
At this point, we need to port OpenMPI to a new system being developed.
I need some help to understand where to start making changes in order to
support this new system, as my search didn't reveal something quite
Hi,
Faster component initialization/finalization times is one of the main
motivating factors of this work. The general idea is to get away from
creating a rather large backing file. With respect to module
bandwidth and latency, mmap and sysv seem to be comparable - at least
that is what
I propose the following for 1.4.2. Can someone double check this?
Index: VERSION
===
--- VERSION (revision 23057)
+++ VERSION (working copy)
@@ -70,17 +70,19 @@
# be affected by changes to inlined functions in OMPI's
# hea
I just updated NEWS on the trunk to reflect all that has happened on the v1.4
branch since 1.4.1:
https://svn.open-mpi.org/trac/ompi/browser/trunk/NEWS#L59
Feel free to edit and correct anything I stated wrong, add issues I missed, etc.
Please review this in the immediate future; it looks l
On Tue, Apr 27, 2010 at 7:55 PM, Samuel K. Gutierrez wrote:
> With Jeff and Ralph's help, I have completed a System V shared memory
> component for Open MPI.
What is the motivation for this work ? Are there situations where the
mmap based SM component doesn't work or is slow(er) ?
Kind regards,
I'm not sure I understand - A and B are in front of the firewall/nat, and C is
behind it? And A and C are the "real" mpi processes, and B is just a proxy?
I'm not sure why you'd need a communication proxy to send all traffic thru;
what you really need is something like a connection manager proxy
