2010-03-04
马少杰
Dear Sir:
I want to use blcr and openmpi to checkpoint, now I can save check
point and restart my work successfully. How erver I find the option "--am
ft-enable-cr" will case large cost . For example , when I run my HPL job
without and with the option "--am ft-ena
On Wed, 2010-03-03 at 12:57 -0500, Prentice Bisbal wrote:
> Reuti wrote:
> > Are you speaking of the same?
>
> Good point, Reuti. I was thinking of a cluster scheduler like SGE or
> Torque.
Yeah, I meant the scheduler in the CPU time slice sense.
http://en.wikipedia.org/wiki/Scheduling_(computi
Hi,
First, I'm hoping setting the subject of this e-mail will get it
attached to the thread that starts with this e-mail:
http://www.open-mpi.org/community/lists/users/2009/12/11608.php
The reason I'm not replying to that thread is that I wasn't subscribed
to the list at the time.
My environm
Hi guys,
Thanks for your help, but unfortunately I am still not clear.
> You are right Dave, FUNNELED allows the application to have multiple
> threads but only the man thread calls MPI.
My understanding is that even if I use SINGLE or MPI_Init, I can still
have multiple threads if I use OpenMP P
On Mar 3, 2010, at 12:16 PM, Prentice Bisbal wrote:
> Eugene Loh wrote:
>> Prentice Bisbal wrote:
>>> Eugene Loh wrote:
>>>
Prentice Bisbal wrote:
> Is there a limit on how many MPI processes can run on a single host?
>
>> Depending on which OMPI release you're using, I think
On Mar 3, 2010, at 3:42 PM, Fernando Lemos wrote:
> On Wed, Mar 3, 2010 at 5:31 PM, Joshua Hursey wrote:
>
>>
>> Yes, ompi-restart should be printing a helpful message and exiting normally.
>> Thanks for the bug report. I believe that I have seen and fixed this on a
>> development branch mak
You are right Dave, FUNNELED allows the application to have multiple
threads but only the man thread calls MPI.
An OpenMP/MPI hybrid program that makes MPI calls only in between parallel
sections is usually a FUNNELED user of MPI
Thanks
Dick Treumann - MPI Team
IBM Systems & Technology Group
On Wed, Mar 3, 2010 at 5:31 PM, Joshua Hursey wrote:
>
> Yes, ompi-restart should be printing a helpful message and exiting normally.
> Thanks for the bug report. I believe that I have seen and fixed this on a
> development branch making its way to the trunk. I'll make sure to move the
> fix t
On Mar 2, 2010, at 9:17 AM, Fernando Lemos wrote:
> On Sun, Feb 28, 2010 at 11:11 PM, Fernando Lemos
> wrote:
>> Hello,
>>
>>
>> I'm trying to come up with a fault tolerant OpenMPI setup for research
>> purposes. I'm doing some tests now, but I'm stuck with a segfault when
>> I try to restart
On Mar 3, 2010, at 11:35 AM, Richard Treumann wrote:
If the application will make MPI calls from multiple threads and
MPI_INIT_THREAD has returned FUNNELED, the application must be
willing to take the steps that ensure there will never be concurrent
calls to MPI from the threads. The threads
Eugene Loh wrote:
> Prentice Bisbal wrote:
>> Eugene Loh wrote:
>>
>>> Prentice Bisbal wrote:
>>>
Is there a limit on how many MPI processes can run on a single host?
> Depending on which OMPI release you're using, I think you need something
> like 4*np up to 7*np (plus a f
Prentice Bisbal wrote:
Eugene Loh wrote:
Prentice Bisbal wrote:
Is there a limit on how many MPI processes can run on a single host?
Depending on which OMPI release you're using, I think you need
something like 4*np up to 7*np (plus a few) descriptor
Eugene Loh wrote:
> Prentice Bisbal wrote:
>
>> Is there a limit on how many MPI processes can run on a single host?
>>
>> I have a user trying to test his code on the command-line on a single
>> host before running it on our cluster like so:
>>
>> mpirun -np X foo
>>
>> When he tries to run it on
Reuti wrote:
> Are you speaking of the same?
Good point, Reuti. I was thinking of a cluster scheduler like SGE or
Torque.
>
> Am 03.03.2010 um 17:32 schrieb Prentice Bisbal:
>
>> Terry Frankcombe wrote:
>>> Surely this is the problem of the scheduler that your system uses,
>
> This I would also
Sorry. I meant to include that. I'm using version 1.2.8.
Ralph Castain wrote:
> It helps to have some idea what version you are talking about...
>
> On Mar 3, 2010, at 9:51 AM, Prentice Bisbal wrote:
>
>> Is there a limit on how many MPI processes can run on a single host?
>>
>> I have a user tr
The caller of MPI_INIT_THREAD says what level of thread safety he would
like to get from the MPI implementation. The implementation says what level
of thread safety it provides.
The implementation is free to provide more or less thread safety than
requested. The caller of MPI_INIT_THREAD should
Are you speaking of the same?
Am 03.03.2010 um 17:32 schrieb Prentice Bisbal:
Terry Frankcombe wrote:
Surely this is the problem of the scheduler that your system uses,
This I would also state.
rather than MPI?
Scheduler in the Linux kernel?
That's not true. The scheduler only assign
Prentice Bisbal wrote:
Is there a limit on how many MPI processes can run on a single host?
I have a user trying to test his code on the command-line on a single
host before running it on our cluster like so:
mpirun -np X foo
When he tries to run it on large number of process (X = 256, 512),
I believe that it specifies the *minimum* threading model supported. If I
recall, opmi is already funnel safe even in single mode. However, if mpi
calls are made from outside the main thread, you should specify funneled for
portability
Brian
On Mar 2, 2010 11:59 PM, "Terry Frankcombe" wrote:
It helps to have some idea what version you are talking about...
On Mar 3, 2010, at 9:51 AM, Prentice Bisbal wrote:
> Is there a limit on how many MPI processes can run on a single host?
>
> I have a user trying to test his code on the command-line on a single
> host before running it on our clu
Is there a limit on how many MPI processes can run on a single host?
I have a user trying to test his code on the command-line on a single
host before running it on our cluster like so:
mpirun -np X foo
When he tries to run it on large number of process (X = 256, 512), the
program fails, and I c
Terry Frankcombe wrote:
> Surely this is the problem of the scheduler that your system uses,
> rather than MPI?
That's not true. The scheduler only assigns the initial processes to
nodes and starts them. It can kill the processes it starts if they use
too much memory or run too long, but doesn't p
It also would have been really helpful to know that you were using MVAPICH and
-not- Open MPI as this mailing list is for the latter. We could have directed
you to the appropriate place if we had known.
On Mar 3, 2010, at 5:17 AM, abc def wrote:
> I don't know (I'm a little new to this area),
I don't know (I'm a little new to this area), but I figured out how to get
around the problem:
Using SGE and MVAPICH2, the "-env MV2_CPU_MAPPING 0:1." option in mpiexec
seems to do the trick.
So when calling the external program with mpiexec, I map the called
process to the current core
I can't speak for the developers. However, I think it's to do with the
library internals.
>From here: http://www.mpi-forum.org/docs/mpi-20-html/node165.htm
"Advice to implementors.
"If provided is not MPI_THREAD_SINGLE then the MPI library should not
invoke C/ C++/Fortran library calls that
Hi all,
I am a beginner of MPI and a little confused with
MPI_Init_thread() function:
If we use MPI_Init() or MPI_Init_thread(MPI_THREAD_SINGLE, provided)
to initialize MPI environment, when we use OpenMP
PARALLEL directive each process is forked to multiple
threads and when an MPI function is ca
Hi all,
I'm playing around with MPI_Comm_spawn, trying to do something simple
with a master-slave example. I get a LOCAL DAEMON SPAWN IS CURRENTLY
UNSUPPORTED error when it tries to spawn the slave. This is on Windows,
OpenMPI version 1.4.1, r22421.
Here's the master code:
int main(int ar
27 matches
Mail list logo
