[OMPI users] Related to project ideas in OpenMPI

[srinivas kundaram]

I am final year grad student looking for my final year project in OpenMPI.We
are group of 4 students.
I wanted to know about the "Process Migration" process of MPI processes in
OpenMPI.
Can anyone suggest me any ideas for project related to process migration in
OenMPI or other topics in Systems.



regards,
Srinivas Kundaram
srinu1...@gmail.com
+91-8149399160

Re: [OMPI users] Related to project ideas in OpenMPI

[Jeff Squyres]

Be aware that process migration is a pretty complex issue.

Josh is probably the best one to answer your question directly, but he's out 
today.


On Aug 24, 2011, at 5:45 AM, srinivas kundaram wrote:

> I am final year grad student looking for my final year project in OpenMPI.We 
> are group of 4 students.
> I wanted to know about the "Process Migration" process of MPI processes in 
> OpenMPI.
> Can anyone suggest me any ideas for project related to process migration in 
> OenMPI or other topics in Systems.
> 
> 
> 
> regards,
> Srinivas Kundaram
> srinu1...@gmail.com
> +91-8149399160
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [OMPI users] Documentation of MPI Implementation

[Jeff Squyres]

On Aug 23, 2011, at 3:32 AM, Hoang-Vu Dang wrote:

> Where could I find a detailed documentation about algorithms that has been 
> using in Open MPI ? 

Unfortunately, you probably won't.

> For example, I would like to answer following questions: how MPI_Algather 
> operation is done? what is the complexity in term of the number of data 
> send/receive given a number of node involved? what is the data structure 
> behind ?. Same as for MPI_Alreduce etc.. 

All of OMPI's collectives are implemented as plugins under the ompi/mca/coll/ 
tree.  There are several different plugins in that tree -- each one has its own 
directory (with the exception of "base", which is glue code for the whole 
collective algorithm framework).  

You probably want to look in the "tuned" component for OMPI's 
current-generation algorithms (to be replaced soon, but that's what's mostly 
used today).  "tuned" has many different algorithm implementations for each MPI 
collective, and uses sophisticated run-time checking to determine which to use.

So the answer to your original query -- how is the MPI_Allgather operation 
done?  -- is, "it depends" on things like message size, number of peers, etc.  
:-)

-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [OMPI users] Documentation of MPI Implementation

[Hoang-Vu Dang]

Thanks Jeff,

I know it depends and I want to know exactly what is the dependency and
general complexity analysis.

Is it really no documentation at all ? For example you said "to be replaced
soon", then what is the algorithms that will be used to replace ? Is there
any publication available ? In another words, how do you know they will be
replaced by which algorithm, please teach me !
Cheers,
Vu

On Wed, Aug 24, 2011 at 9:07 PM, Jeff Squyres  wrote:

> On Aug 23, 2011, at 3:32 AM, Hoang-Vu Dang wrote:
>
> > Where could I find a detailed documentation about algorithms that has
> been using in Open MPI ?
>
> Unfortunately, you probably won't.
>
> > For example, I would like to answer following questions: how MPI_Algather
> operation is done? what is the complexity in term of the number of data
> send/receive given a number of node involved? what is the data structure
> behind ?. Same as for MPI_Alreduce etc..
>
> All of OMPI's collectives are implemented as plugins under the
> ompi/mca/coll/ tree.  There are several different plugins in that tree --
> each one has its own directory (with the exception of "base", which is glue
> code for the whole collective algorithm framework).
>
> You probably want to look in the "tuned" component for OMPI's
> current-generation algorithms (to be replaced soon, but that's what's mostly
> used today).  "tuned" has many different algorithm implementations for each
> MPI collective, and uses sophisticated run-time checking to determine which
> to use.
>
> So the answer to your original query -- how is the MPI_Allgather operation
> done?  -- is, "it depends" on things like message size, number of peers,
> etc.  :-)
>
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>

Re: [OMPI users] Documentation of MPI Implementation

[Jeff Squyres]

On Aug 24, 2011, at 9:14 AM, Hoang-Vu Dang wrote:

> I know it depends and I want to know exactly what is the dependency and 
> general complexity analysis.
> 
> Is it really no documentation at all ?

No, there really isn't (other than the comments in the code).  Sorry.

I think there may have been a paper or two about the general techniques of 
tuned plugin, but it's not going to give you the details of what you want.

> For example you said "to be replaced soon", then what is the algorithms that 
> will be used to replace ? Is there any publication available ? In another 
> words, how do you know they will be replaced by which algorithm, please teach 
> me !

Unfortunately, this is as-yet unpublished work, so I can't really talk about 
any details (I'm not the one doing the work, either).  It's not even in the 
OMPI SVN trunk yet.  This is a fairly common pattern for us; we do 
research-level work off in private branches before bringing the final results 
to the SVN trunk and eventually to an OMPI release branch.

I only mentioned the new stuff because our tuned implementation is a little 
dated; it's fairly obvious that we'd be working on new stuff.  :-)

-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/

[OMPI users] Compiling both 32-bit and 64-bit?

[Dmitry N. Mikushin]

Hi,

Quick question: is there an easy switch to compile and install both
32-bit and 64-bit OpenMPI libraries into a single tree? E.g. 64-bit in
/prefix/lib64 and 32-bit in /prefix/lib.

Thanks,
- D.

Re: [OMPI users] Compiling both 32-bit and 64-bit?

[Barrett, Brian W]

On 8/24/11 11:29 AM, "Dmitry N. Mikushin"  wrote:

>Quick question: is there an easy switch to compile and install both
>32-bit and 64-bit OpenMPI libraries into a single tree? E.g. 64-bit in
>/prefix/lib64 and 32-bit in /prefix/lib.

Quick answer: not easily.

Long answer: There's not an easy way, but there are some facilities to
help.  I believe Oracle uses them when building binaries for Solaris.
There is some documentation available on our Trac wiki:

  https://svn.open-mpi.org/trac/ompi/wiki/MultiLib
  https://svn.open-mpi.org/trac/ompi/wiki/compilerwrapper3264

The difficulty is that it's up to the user/admin to make sure the correct
arguments are provided, as well as writing the wrapper script files to do
the sharing.

Brian

-- 
  Brian W. Barrett
  Dept. 1423: Scalable System Software
  Sandia National Laboratories

Re: [OMPI users] Compiling both 32-bit and 64-bit?

[Dmitry N. Mikushin]

Thanks, Brian,

I'm trying to follow the guide for 1.5.4, not yet clear what's wrong:

[marcusmae@zacate build32]$ ../configure
--prefix=/opt/openmpi_kgen-1.5.4
--includedir=/opt/openmpi_kgen-1.5.4/include/32
--libdir=/opt/openmpi_kgen-1.5.4/lib32 --build=x86_64-unknown-linux
--host=x86_64-unknown-linux --target=i686-unknown-linux
--disable-binaries

...

configure: WARNING: *** The Open MPI configure script does not support
--program-prefix, --program-suffix or --program-transform-name. Users
are recommended to instead use --prefix with a unique directory and
make symbolic links as desired for renaming.
configure: error: *** Cannot continue

[marcusmae@zacate build32]$ ../configure
--prefix=/opt/openmpi_kgen-1.5.4
--includedir=/opt/openmpi_kgen-1.5.4/include/32
--libdir=/opt/openmpi_kgen-1.5.4/lib32 --build=x86_64-unknown-linux
--host=i686-unknown-linux --disable-binaries

...

checking gfortran external symbol convention... link: invalid option -- 'd'
Try `link --help' for more information.
link: invalid option -- 'd'
Try `link --help' for more information.
link: invalid option -- 'd'
Try `link --help' for more information.
link: invalid option -- 'd'
Try `link --help' for more information.
link: invalid option -- 'd'
Try `link --help' for more information.

configure: error: unknown naming convention:

2011/8/24 Barrett, Brian W :
> On 8/24/11 11:29 AM, "Dmitry N. Mikushin"  wrote:
>
>>Quick question: is there an easy switch to compile and install both
>>32-bit and 64-bit OpenMPI libraries into a single tree? E.g. 64-bit in
>>/prefix/lib64 and 32-bit in /prefix/lib.
>
> Quick answer: not easily.
>
> Long answer: There's not an easy way, but there are some facilities to
> help.  I believe Oracle uses them when building binaries for Solaris.
> There is some documentation available on our Trac wiki:
>
>  https://svn.open-mpi.org/trac/ompi/wiki/MultiLib
>  https://svn.open-mpi.org/trac/ompi/wiki/compilerwrapper3264
>
> The difficulty is that it's up to the user/admin to make sure the correct
> arguments are provided, as well as writing the wrapper script files to do
> the sharing.
>
> Brian
>
> --
>  Brian W. Barrett
>  Dept. 1423: Scalable System Software
>  Sandia National Laboratories
>
>
>
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>

Re: [OMPI users] Compiling both 32-bit and 64-bit?

[Barrett, Brian W]

Can you try to build without specifying the --build, --host, and --target
options and just specifying the various FLAGS options as either -m32 or
-m64 as appropriate?  If that doesn't clean things up, can you include all
the information requested here:

  http://www.open-mpi.org/community/help/

Thanks,

Brian

On 8/24/11 1:15 PM, "Dmitry N. Mikushin"  wrote:

>Thanks, Brian,
>
>I'm trying to follow the guide for 1.5.4, not yet clear what's wrong:
>
>[marcusmae@zacate build32]$ ../configure
>--prefix=/opt/openmpi_kgen-1.5.4
>--includedir=/opt/openmpi_kgen-1.5.4/include/32
>--libdir=/opt/openmpi_kgen-1.5.4/lib32 --build=x86_64-unknown-linux
>--host=x86_64-unknown-linux --target=i686-unknown-linux
>--disable-binaries
>
>...
>
>configure: WARNING: *** The Open MPI configure script does not support
>--program-prefix, --program-suffix or --program-transform-name. Users
>are recommended to instead use --prefix with a unique directory and
>make symbolic links as desired for renaming.
>configure: error: *** Cannot continue
>
>[marcusmae@zacate build32]$ ../configure
>--prefix=/opt/openmpi_kgen-1.5.4
>--includedir=/opt/openmpi_kgen-1.5.4/include/32
>--libdir=/opt/openmpi_kgen-1.5.4/lib32 --build=x86_64-unknown-linux
>--host=i686-unknown-linux --disable-binaries
>
>...
>
>checking gfortran external symbol convention... link: invalid option --
>'d'
>Try `link --help' for more information.
>link: invalid option -- 'd'
>Try `link --help' for more information.
>link: invalid option -- 'd'
>Try `link --help' for more information.
>link: invalid option -- 'd'
>Try `link --help' for more information.
>link: invalid option -- 'd'
>Try `link --help' for more information.
>
>configure: error: unknown naming convention:
>
>2011/8/24 Barrett, Brian W :
>> On 8/24/11 11:29 AM, "Dmitry N. Mikushin"  wrote:
>>
>>>Quick question: is there an easy switch to compile and install both
>>>32-bit and 64-bit OpenMPI libraries into a single tree? E.g. 64-bit in
>>>/prefix/lib64 and 32-bit in /prefix/lib.
>>
>> Quick answer: not easily.
>>
>> Long answer: There's not an easy way, but there are some facilities to
>> help.  I believe Oracle uses them when building binaries for Solaris.
>> There is some documentation available on our Trac wiki:
>>
>>  https://svn.open-mpi.org/trac/ompi/wiki/MultiLib
>>  https://svn.open-mpi.org/trac/ompi/wiki/compilerwrapper3264
>>
>> The difficulty is that it's up to the user/admin to make sure the
>>correct
>> arguments are provided, as well as writing the wrapper script files to
>>do
>> the sharing.
>>
>> Brian
>>
>> --
>>  Brian W. Barrett
>>  Dept. 1423: Scalable System Software
>>  Sandia National Laboratories
>>
>>
>>
>>
>>
>> ___
>> users mailing list
>> us...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/users
>>
>
>___
>users mailing list
>us...@open-mpi.org
>http://www.open-mpi.org/mailman/listinfo.cgi/users
>
>


-- 
  Brian W. Barrett
  Dept. 1423: Scalable System Software
  Sandia National Laboratories