Dear all,
I'm trying to use MPI_ACCUMULATE with a user-defined datatype.
Basically, I want to be able to accumulate a subset of a
three-dimensional array, but since the data is non-contiguous in memory,
it requires defining a new type with MPI_TYPE_VECTOR and MPI_TYPE_HVECTOR.
I wrote a simple pr
On Aug 20, 2009, at 3:37 PM, Jean Potsam wrote:
Dear All,
I tried to install openmpi 1.3 in my home directory on
one of the nodes of our cluster. I have adminsitrative rights and is
installing as a superuser. The configure phase is fine. The make all
install part give me the f
Dear All,
I tried to install openmpi 1.3 in my home directory on one of the
nodes of our cluster. I have adminsitrative rights and is installing as a
superuser. The configure phase is fine. The make all install part give me the
following problems:
##
On Aug 20, 2009, at 5:14 AM, tomek wrote:
Is doing blocking communication in a separate thread better then
asynchronous progress?
(At least as a workaround until the proper implementation gets
improved)
At the moment, yes. OMPI's asynchronous progress is "loosely
tested" (at best).
O
On Aug 19, 2009, at 7:48 PM, tomek wrote:
Now that I have complied my code with OpenMPI 1.3.3 here is a new
problem:
When asynchronous progress is enabled even a simplest test problems
run extremely slowly.
What's "extremely slowly", and what does your test program do?
By "asynchronous pro
Hi
Since I discovered, that asynchronous progress does not work too well,
here is my question:
Is doing blocking communication in a separate thread better then
asynchronous progress?
(At least as a workaround until the proper implementation gets improved)
Of course I will test it, but per
