You apparently are running on a cluster that uses Torque, yes? If so, it won't
use ssh to do the launch - it uses Torque to do it, so the passwordless ssh
setup is irrelevant.
Did you ensure that your LD_LIBRARY_PATH includes the OMPI install lib location?
On May 3, 2012, at 9:59 AM, Acero Fer
Hello,
I have a problem when running a mpi program with openmpi library. I did the
following.
1.- I installed the ofed 1.5.4 from RHEL. The hardware are qlogic 7340 ib
cards.
2.- I am using openmpi 1.4.3 , the one that comes with ofed 1.5.4
3.- I have check openmpi website, and I have all
On Jan 12, 2010, at 16:57 , Eugene Loh wrote:
> Jeff Squyres wrote:
>
>> It would be very strange for nanosleep to cause a problem for Open MPI -- it
>> shouldn't interfere with any of Open MPI's mechanisms. Double check that
>> your my_barrier() function is actually working properly -- remov
Jeff Squyres wrote:
It would be very strange for nanosleep to cause a problem for Open MPI -- it
shouldn't interfere with any of Open MPI's mechanisms. Double check that your
my_barrier() function is actually working properly -- removing the nanosleep()
shouldn't affect the correctness of yo
It would be very strange for nanosleep to cause a problem for Open MPI -- it
shouldn't interfere with any of Open MPI's mechanisms. Double check that your
my_barrier() function is actually working properly -- removing the nanosleep()
shouldn't affect the correctness of your barrier.
If you'v
First of all, the reason that I have created a CPU-friendly version of
MPI_Barrier is that my program is asymmetric (so some of the nodes can
easily have to wait for several hours) and that it is I/O bound. My program
uses MPI mainly to synchronize I/O and to share some counters between the
nodes,
On Sun, 2009-12-13 at 19:04 +0100, Gijsbert Wiesenekker wrote:
> The following routine gives a problem after some (not reproducible)
> time on Fedora Core 12. The routine is a CPU usage friendly version of
> MPI_Barrier.
There are some proposals for Non-blocking collectives before the MPI
forum cu
Let's start with this: You generate non-blocking sends (MPI_Isend).
Those sends are not completed anywhere. So, strictly speaking, they
don't need to be executed. In practice, even if they are executed, they
should be "completed" from the user program's point of view (MPI_Test,
MPI_Wait, MP
The following routine gives a problem after some (not reproducible) time on
Fedora Core 12. The routine is a CPU usage friendly version of MPI_Barrier.
The verbose output shows that if the problem occurs one of the (not
reproducible) nodes does not receive a message from one of the other (not
re
Calin
Your questions don't belong in this forum. You either need to be computer
literate (your questions are basic OS related) or delegate this task to
someone more experienced.
Good luck
Durga
On 11/3/06, calin pal wrote:
/*please read the mail and ans my query*/
sir,
in f
I thought that George answered your mail already...?
http://www.open-mpi.org/community/lists/users/2006/11/2102.php
On Nov 3, 2006, at 5:29 AM, calin pal wrote:
/*please read the mail and ans my query*/
sir,
in four machine of our college i have installed in this
way..tha
/*please read the mail and ans my query*/
sir,
in four machine of our college i have installed in this way..that i
m sending u
i start four machine from root...
then i installed the openmpi1.1.1 -tar.gz using the commands.
tar -xvzf openmpi-1.1.1
cd openmpi-1.1.1
./configu
sir,
in four machine of our college i have installed in this way..that i
m sending u
i start four machine from root...
then i installed the openmpi1.1.1 -tar.gz using the commands.
tar -xvzf openmpi-1.1.1
cd openmpi-1.1.1
./configure --prefix=/usr/local
make
make all install
ompi_
13 matches
Mail list logo
