[OMPI devel] MPI_Win_get_group

The MPI-2 standard says (see bottom of ) MPI_WIN_GET_GROUP returns a duplicate of the group of the communicator used to create the window. associated with win. The group is returned in group. Pease, note the 'duplicate' ... Well, it

[OMPI devel] FW: [RFC] Sparse group implementation]

I Updated the RFC.. > From: Jeff Squyres > Date: July 25, 2007 9:04:44 AM EDT > To: Open Developers > Subject: [OMPI devel] [RFC] Sparse group implementation > Reply-To: Open MPI Developers > > WHAT:Merge the sparse groups work to the trunk; get the > community's > opinion on one

Re: [OMPI devel] COVERITY STATIC SOURCE CODE ANALYSIS

It's been finalized: Coverity has formally joined the Open MPI Project as a Partner (OMPI web page updates will come soon). They will be running the Open MPI source code base through their tools on a regular basis and making the results available to Members of the Open MPI project. The s

Re: [OMPI devel] Hostfiles - yet again

You were limpid. What we're trying to say here, it's that the solution you described few emails ago, doesn't work. At least it doesn't work for what we want to do (i.e. what Aurelien described in his first email). We [really] need 2 separate MPI worlds, that we will connect at a later momen

Re: [OMPI devel] Hostfiles - yet again

Guess I was unclear, George - I don't know enough about Aurelien's app to know if it is capable of (or trying to) run as one job, or not. What has been described on this thread to-date is, in fact, a corner case. Hence the proposal of another way to possibly address a corner case without disruptin

Re: [OMPI devel] [RFC] New command line options to replace persistent daemon operations

I basically agree with Terry, even if your proposal would solve all the issue I currently face. I think we need to read the MPI2 standard to make sure we are not on the brink of breaking the standard. Aurelien On Jul 27, 2007, at 10:13 , Ralph Castain wrote: On 7/27/07 7:58 AM, "Terry

Re: [OMPI devel] Hostfiles - yet again

It's not about the app. It's about the MPI standard. With one mpirun you start one MPI application (SPMD or MPMD but still only one). The first impact of this, is all processes started with one mpirun command will belong to the same MPI_COMM_WORLD. Our mpirun is in fact equivalent to the mp

[OMPI devel] minor bug report for building openmpi-1.2.3 on cygwin

Hi, I've just built and installed openmpi-1.2.3 on cygwin. It seems that most files depend on opal/mca/timer/windows/timer_windows.h, but opal/mca/timer/windows/timer_windows_component.c depends on opal/timer/windows/timer_windows_component.h (which doesn't exist). I simply copied timer_win

Re: [OMPI devel] [RFC] New command line options to replace persistent daemon operations

On 7/27/07 7:58 AM, "Terry D. Dontje" wrote: > Ralph Castain wrote: > >> WHAT: Proposal to add two new command line options that will allow us to >>replace the current need to separately launch a persistent daemon to >>support connect/accept operations >> >> WHY:Remove

Re: [OMPI devel] [RFC] New command line options to replace persistent daemon operations

Ralph Castain wrote: WHAT: Proposal to add two new command line options that will allow us to replace the current need to separately launch a persistent daemon to support connect/accept operations WHY:Remove problems of confusing multiple allocations, provide a cleaner

[OMPI devel] [RFC] New command line options to replace persistent daemon operations

WHAT: Proposal to add two new command line options that will allow us to replace the current need to separately launch a persistent daemon to support connect/accept operations WHY:Remove problems of confusing multiple allocations, provide a cleaner method for connect/

Re: [OMPI devel] Hostfiles - yet again

On 7/26/07 4:22 PM, "Aurelien Bouteiller" wrote: >> mpirun -hostfile big_pool -n 10 -host 1,2,3,4 application : -n 2 -host >> 99,100 ft_server > > This will not work: this is a way to launch MIMD jobs, that share the > same COMM_WORLD. Not the way to launch two different applications that > i

Re: [OMPI devel] [OMPI svn] svn:open-mpi r15661

On Jul 27, 2007, at 6:00 AM, Bert Wesarg wrote: Passing NULL to pthread_exit() is verbotten. Why? I can't find anything in the standard or is it some OMPI internal? The man page for pthread_exit(1) on Linux does not specifically say that NULL is allowed. Plus, on RHEL4 when using the TLS

Re: [OMPI devel] [OMPI svn] svn:open-mpi r15661

> Author: jsquyres > Date: 2007-07-26 21:06:36 EDT (Thu, 26 Jul 2007) > New Revision: 15661 > URL: https://svn.open-mpi.org/trac/ompi/changeset/15661 > > Log: > Passing NULL to pthread_exit() is verbotten. Why? I can't find anything in the standard or is it some OMPI internal? Bert