Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2007-03-22 07:19:02


FWIW, I believe that we had intended --prefix to handle simple cases
which is why this probably doesn't work for you. But as long as the
different prefixes are specified for different nodes, it could
probably be made to work.

Which launcher are you using this with?

On Mar 21, 2007, at 11:36 PM, Ralph Castain wrote:

> Yo David
>
> What system are you running this on? RoadRunner? If so, I can take
> a look at
> "fixing" it for you tomorrow (Thurs).
>
> Ralph
>
>
> On 3/21/07 10:17 AM, "David Daniel" <ddd_at_[hidden]> wrote:
>
>> I'm experimenting with heterogeneous applications (x86_64 <-->
>> ppc64), where the systems share the file system where Open MPI is
>> installed.
>>
>> What I would like to be able to do is something like this:
>>
>> mpirun --np 1 --host host-x86_64 --prefix /opt/ompi/x86_64
>> a.out.x86_64 : --np 1 --host host-ppc64 --prefix /opt/ompi/ppc64
>> a.out.ppc64
>>
>> Unfortunately it looks as if the second --prefix is always ignored.
>> My guess is that orte_app_context_t::prefix_dir is getting set, but
>> only the 0th app context is never consulted (except in the dynamic
>> process stuff where I do see a loop over the app context array).
>>
>> I can of course work around it with startup scripts, but a command
>> line solution would be attractive.
>>
>> This is with openmpi-1.2.
>>
>> Thanks, David
>>
>> _______________________________________________
>> devel mailing list
>> devel_at_[hidden]
>> http://www.open-mpi.org/mailman/listinfo.cgi/devel
>
>
> _______________________________________________
> devel mailing list
> devel_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/devel

-- 
Jeff Squyres
Cisco Systems