That would make sense. I able to break OpenMPI by having Node A wait for
messages from Node B. Node B is in fact sleeping while Node C bombards
Node A with a few thousand messages. After a while Node B wakes up and
sends Node A the message it's been waiting on, but Node A has long since
been buried
The Voltaire tech was right. There is no credit management at the
upper level, each BTL is allowed to do it (if needed). This doesn't
means the transport is not reliable. Most of the devices have internal
flow control, and Open MPI rely on it instead of implementing our own.
However, the de
Hi,
I am readying an openmpi 1.2.5 software stack for use with a
many-thousand core cluster. I have a question about sending small
messages that I hope can be answered on this list.
I was under the impression that if node A wants to send a small MPI
message to node B, it must have a credit to do
I'm working on a rather eccentric application of openmpi. Is there
any way to dynamically change the information obtained from the
machine or hosts file provided on the command line to mpirun?
Perhaps something like:
MPI_Reread_Hosts( const char* hfilepath );
Many thanks in advance,
--
Keith
I don't know of any work in that direction for now. Indeed, we plan to
eventually integrate at least causal message logging in the pml-v,
which also includes piggybacking. Therefore we are open for
collaboration with you on this matter. Please let us know :)
Aurelien
Le 1 févr. 08 à 09:5
Hi,
I'm currently working on optimistic message logging and I would like to
implement an optimistic message logging protocol in OpenMPI. Optimistic
message logging protocols piggyback information about dependencies
between processes on the application messages to be able to find a
consistent
I can replicate the problem even with 7.0-7. Unfortunately, we're
using a standard GNU Autoconf test in OMPI's configure to get the size:
AC_CHECK_SIZE(bool)
I'm not quite sure why it doesn't work with the PGI 7.0 compiler
series and those particular options. :-\
On Jan 31, 2008, at 7
On Thu, 2008-01-31 at 16:01 -0800, Adam Moody wrote:
> Here is some more info. The build works if I do either of:
>
> (1) Build with PGI v7.1-3 instead of PGI v7.0-3
> (2) Or, drop the "-g" option in CXXFLAGS, i.e.,
> change:
> CXXFLAGS="-Msignextend -g -O2"
> to just:
> CXXFLAGS="-Msig
