On 2/1/2011 5:02 PM, Jeffrey A Cummings wrote:
I use OpenMPI on a variety of platforms: stand-alone servers running
Solaris on sparc boxes and Linux (mostly CentOS) on AMD/Intel boxes,
also Linux (again CentOS) on large clusters of AMD/Intel boxes. These
platforms all have some version of the 1.3
Thanks for all the good replies on this thread. I don't know if I'll be
able to make a dent in the corporate IT bureaucracy but I'm going to try.
From: Prentice Bisbal
To: Open MPI Users
List-Post: users@lists.open-mpi.org
Date: 02/02/2011 11:35 AM
Subject:Re: [OMPI users] H
The context was wrt the OpenMPI version that is bundled with a specific
version of CentOS Linux which my IT folks are about to install on one of
our servers. Since the most recent 1.4 stream version is 1.4.3, I'm
afraid that 1.4-4 is really some variant of 1.4 (i.e., 1.4.0) and hence
not that
Again, you can try the Peruse instrumentation. Configure OMPI with
--enable-peruse. The instrumentation points might help you decide how
you want to define the time you want to measure. Again, you really have
to spend a bunch of your own time deciding what is meaningful to measure.
Gustavo
On Feb 2, 2011, at 1:44 PM, Jeffrey A Cummings wrote:
> I've encountered a supposed OpenMPI version of 1.4-4. Is the hyphen a typo
> or is this syntax correct and if so what does it mean?
Is this an RPM version number? It's fairly common for RPMs to add "-X" at the
end of the version number.
On Feb 2, 2011, at 7:35 AM, Bibrak Qamar wrote:
> Gus Correa, But it will include the time of computation which took place
> before waitAll( ).
>
Correct.
Now I realize you want the communication time only,
not the overall time.
Even to define precisely what this means may be a bit tricky.
I g
I think ultimately it would comes down to whether code execution is
more important than receiving the message in a timely fashion.
On 2/2/11, amjad ali wrote:
> Perhaps often it is more useful to use MPI_WAIT rather than MPI_TEST type
> fucntions, because at MPI_WAIT point it will be taken care o
Perhaps often it is more useful to use MPI_WAIT rather than MPI_TEST type
fucntions, because at MPI_WAIT point it will be taken care of communication
completion, automatically, which may be necessary before going ahead. with
MPI_TEST it would become the responsibility of the programmer to handle th
I've encountered a supposed OpenMPI version of 1.4-4. Is the hyphen a
typo or is this syntax correct and if so what does it mean?
- Jeff
Thaks all
I did the simple copying of the 32Bit applications and now it works.
Thanks
Jody
On Wed, Feb 2, 2011 at 5:47 PM, David Mathog wrote:
> jody wrote:
>
>> How can i force OpenMPI to be built as a 32Bit application on a 64Bit
> machine?
>
> THe easiest way is not to - just copy over a
Hi,
We'll try to reproduce the problem.
Thanks,
--
Samuel K. Gutierrez
Los Alamos National Laboratory
On Feb 2, 2011, at 2:55 AM, Michael Curtis wrote:
On 28/01/2011, at 8:16 PM, Michael Curtis wrote:
On 27/01/2011, at 4:51 PM, Michael Curtis wrote:
Some more debugging information:
Is
jody wrote:
> How can i force OpenMPI to be built as a 32Bit application on a 64Bit
machine?
THe easiest way is not to - just copy over a build from a 32 bit
machine, it will run on your 64 bit machine if the proper 32 bit
libraries have been installed there. Otherwise, you need to put -m32
on
Jeffrey A Cummings wrote:
> I use OpenMPI on a variety of platforms: stand-alone servers running
> Solaris on sparc boxes and Linux (mostly CentOS) on AMD/Intel boxes,
> also Linux (again CentOS) on large clusters of AMD/Intel boxes. These
> platforms all have some version of the 1.3 OpenMPI stre
jody wrote:
Thanks for your reply.
If i try your suggestion, every process fails with the following message:
*** The MPI_Init() function was called before MPI_INIT was invoked.
That's a funny error message. If you search the OMPI users mail list
archives, this message shows up, but I didn
Bibrak Qamar wrote:
Gus Correa, But it will include the time of
computation which took place before waitAll( ).
What's wrong with that?
From: Bibrak Qamar
I am using non-blocking send and receive, and i want to calculate the
time
it took for the communication.
F
Hey,
I work for Platform Computing, we do have our clustering tool as well
and I play a lot with others (PCM, ROCKS, xCAT, Unicluster ...). I never
ran into any problem switching OpenMPI versions. In my case I use
environment modules and it just works like a charm :-) You can also have
modules dep
On Feb 2, 2011, at 7:02 AM, Terry Dontje wrote:
> 2. The system libraries on different linux versions are not always the same.
> At Oracle we build a binary distribution of OMPI that we test out on several
> different versions of Linux. The key here is building on a machine that is
> essenti
Yes; you can use any of the various flavors of the MPI_TEST* functions.
On Feb 2, 2011, at 7:03 AM, Bibrak Qamar wrote:
> Hello All,
>
> Is there any way to find whether a non blocking communication has finished
> without calling the wait( ) function.
>
>
> Thanks
> Bibrak Qamar
> Undergradua
Gus Correa, But it will include the time of computation which took place
before waitAll( ).
List-Post: users@lists.open-mpi.org
Date: Tue, 1 Feb 2011 10:09:03 +0400
From: Bibrak Qamar
Subject: [OMPI users] Calculate time spent on non blocking
communication?
To: us...@open-mpi.org
Message-
Hello All,
Is there any way to find whether a non blocking communication has finished
without calling the wait( ) function.
Thanks
Bibrak Qamar
Undergraduate Student BIT-9
Member Center for High Performance Scientific Computing
NUST-School of Electrical Engineering and Computer Science.
On 02/01/2011 07:34 PM, Jeff Squyres wrote:
On Feb 1, 2011, at 5:02 PM, Jeffrey A Cummings wrote:
I'm getting a lot of push back from the SysAdmin folks claiming that OpenMPI is
closely intertwined with the specific version of the operating system and/or
other system software (i.e., Rocks on
On 28/01/2011, at 8:16 PM, Michael Curtis wrote:
>
> On 27/01/2011, at 4:51 PM, Michael Curtis wrote:
>
> Some more debugging information:
Is anyone able to help with this problem? As far as I can tell it's a
stock-standard recently installed SLURM installation.
I can try 1.5.1 but hesitant
Jody,
With the gnu compilers the -m32 flag works. With other compilire's the same or
other flag should work.
Doug Reeder
On Feb 1, 2011, at 11:46 PM, jody wrote:
> Thanks for your reply.
>
> If i try your suggestion, every process fails with the following message:
>
> *** The MPI_Init() fun
Thanks for your reply.
If i try your suggestion, every process fails with the following message:
*** The MPI_Init() function was called before MPI_INIT was invoked.
*** This is disallowed by the MPI standard.
*** Your MPI job will now abort.
[aim-triops:15460] Abort before MPI_INIT completed succ
24 matches
Mail list logo