Re: Dynamic Process comment: using MPI_Init() without mpirun
Gary Oberbrunner (firstname.lastname@example.org)
Mon, 29 Apr 1996 18:38:44 -0400
> Date: Mon, 29 Apr 1996 15:34:24 -0700
> From: "Eric Salo" <email@example.com>
> > With such a function we could dispense with mpirun and friends
> > altogether, and any application could just use this function to
> > "become" the first process, and then spawn all the rest of the
> > processes.
> But what if your execution model is to start all of your processes
> at once, and you are in fact not even allowed to spawn new ones?
> (I'm thinking of some of the MPPs.) It's not clear that all
> architectures will be able to support the dynamic process
> chapter. At the moment, these machines are capable of supporting
> the semantics of MPI_Init() as it currently stands. This would
> break that, I think.
Yeah, I agree. I think all we want to say is that *if* the
implementation supports dynamic processes, then a "bare" (in a proc
not created by mpirun or spawn) MPI_Init creates a singleton MPI app.
If not, then I'm comfortable leaving the result undefined, since it
works as best it can currently.
Gary Oberbrunner firstname.lastname@example.org
Advanced Visual Systems, Inc. http://www.avs.com/~garyo
300 Fifth Avenue (617)890-8192 x2133 TEL
Waltham, MA 02154 (617)890-8287 FAX