[mvapich-discuss] Does ch3:mrail support dynamic processes

Jonathan Perkins perkinjo at cse.ohio-state.edu
Tue Dec 11 10:30:24 EST 2012


Hello John.  MVAPICH2 supports Dynamic Process Management when you set
the environment variable MV2_SUPPORT_DPM to 1.  Please see the following
taken from our 1.9a2 userguide.

http://mvapich.cse.ohio-state.edu/support/user_guide_mvapich2-1.9a2.html#x1-350005.2.5

5.2.5 Run with Dynamic Process Management support

MVAPICH2 (OFA-IB-CH3 interface) provides MPI-2 dynamic process management. This feature allows MPI applications to spawn new MPI processes according to MPI-2 semantics. The following commands provide an example of how to run your application.

    To run your application using mpirun_rsh
        $ mpirun_rsh -np 2 -hostfile hosts MV2_SUPPORT_DPM=1 ./spawn1

    Note: It is necessary to provide the hostfile when running dynamic
    process management applications using mpirun_rsh.

    To run your application using mpiexec (Hydra)
        $ mpiexec -n 2 -f hosts -env MV2_SUPPORT_DPM 1 ./spawn1 

On Tue, Dec 11, 2012 at 05:05:00PM +0200, John Gilmore wrote:
> Dear all,
> 
> I've been working with Open MPI for a while now and have decided to move our implementation to MVAPICH2 to make use of the specialised Infiniband features of MVAPCH2 and hopefully get some extra performance out of our implementation.
> 
> The problem that I now have is that the MVAPICH2 implementation does not seem to support dynamic processes. Specifically the client/server functionality of MPI (Open_port, connect, accept).
> 
> The reason I'm saying this is I'm using the CH3:mrail channel and I get the error: MPI_ERR_OTHER error when I call MPI_Open_port and the connect and accept functions. After looking through the code, I found the MPID_Open_port function, which can return the MPI_ERR_OTHER error along with a string "**notimpl". This seems to be the error that I'm getting, although I could not find a way to access that "**notimpl" string when the error returns.
> 
> In the function comments it states:
> /* The default for this function is MPIDI_Open_port.
>        A channel may define its own function and set it in the 
>        init check above; such a function may be named MPIDI_CH3_Open_port.
>        In addition, not all channels can implement this operation, so
>        those channels will set the function pointer to NULL */
> 
> So I have the following questions:
> Does ch3:mrail support the client/server function of MPI? If so, am I missing something?
> How can I access the message that is set in the MPIU_ERR_SET function?
> 
> I'd really appreciate your time and assistance.
> Regards
> John Gilmore 



> _______________________________________________
> mvapich-discuss mailing list
> mvapich-discuss at cse.ohio-state.edu
> http://mail.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss


-- 
Jonathan Perkins
http://www.cse.ohio-state.edu/~perkinjo



More information about the mvapich-discuss mailing list