- discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] [PATCH v2] test: add attrdeleteget, MPI_Attr_get called from delete_fn
by Pavan Balaji 20 May '13

20 May '13

On 05/20/2013 08:55 AM US Central Time, Jeff Squyres (jsquyres) wrote: > On May 20, 2013, at 9:52 AM, Pavan Balaji <balaji(a)mcs.anl.gov> wrote: > >> As nasty as it is, apart from implementation difficulty, what's the >> problem with it in the standard (apart from wording clarification)? > > The standard doesn't say what you're allowed (or not allowed) to do at all. Yes, I'm looking at this as wording clarification. Right now, since the standard doesn't disallow it, applications use it as if it's allowed. > For example, can you call MPI_SEND from within an attribute call back? Or MPI_COMM_SPAWN? Yes to both. > And what about the non-deterministic effects that I called out in the > email back in 2011 -- are those allowed, and if so, do we need to say > that they're non-deterministic? ...and so on.- Right, we did talk about the non-determinism on this email thread before you joined in, but we concluded that there's only one sensible way. Of course, that should be clarified in the standard. But it's not a major change in implementations, I think. -- Pavan - Pavan Balaji http://www.mcs.anl.gov/~balaji

1 0

Re: [mpich-discuss] [PATCH v2] test: add attrdeleteget, MPI_Attr_get called from delete_fn
by Jeff Squyres (jsquyres) 20 May '13

20 May '13

On May 20, 2013, at 9:52 AM, Pavan Balaji <balaji(a)mcs.anl.gov> wrote: > As nasty as it is, apart from implementation difficulty, what's the > problem with it in the standard (apart from wording clarification)? The standard doesn't say what you're allowed (or not allowed) to do at all. For example, can you call MPI_SEND from within an attribute call back? Or MPI_COMM_SPAWN? And what about the non-deterministic effects that I called out in the email back in 2011 -- are those allowed, and if so, do we need to say that they're non-deterministic? ...and so on. -- Jeff Squyres jsquyres(a)cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

1 0

Re: [mpich-discuss] [PATCH v2] test: add attrdeleteget, MPI_Attr_get called from delete_fn
by Pavan Balaji 20 May '13

20 May '13

On 05/20/2013 08:39 AM US Central Time, Jeff Squyres (jsquyres) wrote: > 1. What exactly is allowed to be done in attribute callbacks (or any > callbacks, actually) -- to include whether you can GET_ATTR, etc. I might have missed this at the Forum. This issue came up within MPICH some time back. Right now, since the standard is so restrictive, we had to make a bunch of our functions reentrant-safe to allow for this case (though I'm sure we missed a few). As nasty as it is, apart from implementation difficulty, what's the problem with it in the standard (apart from wording clarification)? -- Pavan -- Pavan Balaji http://www.mcs.anl.gov/~balaji

1 0

Re: [mpich-discuss] [PATCH v2] test: add attrdeleteget, MPI_Attr_get called from delete_fn
by Jeff Squyres (jsquyres) 20 May '13

20 May '13

On May 18, 2013, at 4:41 PM, Fab Tillier <ftillier(a)microsoft.com> wrote: > I agree the standard should clarify (I'll take a look at the ticket you created), and I'd like to see a clarification of the behavior with respect to the attribute delete callbacks. Specifically, the standard does not state explicitly whether the attributes are destroyed within the call to MPI_COMM_FREE, or only once all references on the communicator are released. Sorry for jumping in late... I actually brought this exact issue up with the Forum a few years ago. There's a few larger issues: 1. What exactly is allowed to be done in attribute callbacks (or any callbacks, actually) -- to include whether you can GET_ATTR, etc. 2. Is the Fortran attribute extra state parameter passed by value or by reference? Sadly, it looks like I only made a ticket on #2: https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/159 But for #1, there was some web discussion about this, but the issue never really went anywhere. Here's the first mail about it, from back in 2011: http://lists.mpi-forum.org/mpi-forum/2011/04/1035.php -- Jeff Squyres jsquyres(a)cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

1 0

Re: [mpich-discuss] Porting MPICH
by jhonatan alves 20 May '13

20 May '13

Hello, Today we will try the strategies proposed by you and see how it goes. Thank you for helping 2013/5/19 Jeff Hammond <jhammond(a)alcf.anl.gov> > Yeah, I would use the abort strategy to detect if MPICH is using > thread-related functions in MPI_THREAD_SINGLE (ignoring > MPICH_ASYNC_PROGRESS=1) and the noop implementation for practical > purposes. > > Jeff > > On Sun, May 19, 2013 at 2:49 PM, Pavan Balaji <balaji(a)mcs.anl.gov> wrote: > > > > Thanks. Yes, they can be mostly no-ops (except TLS checks which can be > > any static variable since there's only one thread by definition). > > Implementing them as "not-implemented" aborts might be OK too. > > > > -- Pavan > > > > On 05/19/2013 02:43 PM US Central Time, Jeff Hammond wrote: > >> Presumably those functions can be noops if no threads are going to be > >> used. Am I wrong? > >> > >> It might be worth implementing those functions as stubs that abort > >> with UNIMPL error and see how far that goes. I'll try to get to this > >> later today. > >> > >> Jeff > >> > >> On Sun, May 19, 2013 at 2:36 PM, Pavan Balaji <balaji(a)mcs.anl.gov> > wrote: > >>> > >>> On 05/19/2013 02:28 PM US Central Time, jhonatan alves wrote: > >>>> But i believe that the missing of POSIX > >>>> threads can be the most trouble part. So we need to port to the thread > >>>> implementation in EPOS. > >>> > >>> Yup, I too believe that'll be the blocker. MPICH supports multiple > >>> threading packages, but currently requires at least one to function > >>> correctly: > >>> > >>> https://trac.mpich.org/projects/mpich/ticket/231 > >>> > >>> It's been a while since I looked into this issue, but I could look into > >>> it if you are running into it for your platform. > >>> > >>> -- Pavan > >>> > >>> -- > >>> Pavan Balaji > >>> http://www.mcs.anl.gov/~balaji > >>> _______________________________________________ > >>> discuss mailing list discuss(a)mpich.org > >>> To manage subscription options or unsubscribe: > >>> https://lists.mpich.org/mailman/listinfo/discuss > >> > >> > >> > > > > -- > > Pavan Balaji > > http://www.mcs.anl.gov/~balaji > > > > -- > Jeff Hammond > Argonne Leadership Computing Facility > University of Chicago Computation Institute > jhammond(a)alcf.anl.gov / (630) 252-5381 > http://www.linkedin.com/in/jeffhammond > https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond > ALCF docs: http://www.alcf.anl.gov/user-guides >

1 0

Re: [mpich-discuss] checkpoint error
by Jeff Hammond 19 May '13

19 May '13

What Ralf was trying to point out is that you used /home/buntinas in a path. That home directory was likely cut-and-paste from an example created by Darius Buntinas, a developer of MPICH. It is almost certainly not a valid path on your machine. Your home directory appears to be /home/basma/, which makes sense given your name. When Ralf said "It sounds like that path should be something like /home/basma/ckpts/app.ckpoint instead," he was not suggesting that you blindly cut-and-paste that path and assume it would work. The use of "something like" was meant to provoke some analysis on your part that would lead to you identify the appropriate path to use there. I am tempted to suggest that you use "-ckpoint-prefix /dev/null", which will probably work (just not the way you might like), but I am afraid that you will not internalize what I'm trying to say and actually follow that advice. Jeff On Sun, May 19, 2013 at 4:33 PM, basma a.azeem <basmaabdelazeem(a)hotmail.com> wrote: > same error > > basma@basma-Satellite-A500:~$ mpiexec -ckpointlib blcr -ckpoint-prefix > /home/basma/ckpts/app.ckpoint -ckpoint-interval 1 -n 4 > /home/basma/NPB3.3/NPB3.3/NPB3.3-MPI/bin/is.A.4 > > > > NAS Parallel Benchmarks 3.3 -- IS Benchmark > > Size: 8388608 (class A) > Iterations: 100 > Number of processes: 4 > > iteration > 1 > 2 > 3 > 4 > 5 > 6 > 7 > 8 > 9 > 10 > 11 > > [proxy:0:0@basma-Satellite-A500] requesting checkpoint > [proxy:0:0@basma-Satellite-A500] HYDT_ckpoint_checkpoint > (./tools/ckpoint/ckpoint.c:106): Failed to stat checkpoint prefix > "/home/basma/ckpts/app.ckpoint": No such file or directory > > [proxy:0:0@basma-Satellite-A500] HYD_pmcd_pmip_control_cmd_cb > (./pm/pmiserv/pmip_cb.c:905): checkpoint suspend failed > [proxy:0:0@basma-Satellite-A500] HYDT_dmxu_poll_wait_for_event > (./tools/demux/demux_poll.c:77): callback returned error status > [proxy:0:0@basma-Satellite-A500] main (./pm/pmiserv/pmip.c:206): demux > engine error waiting for event > [mpiexec@basma-Satellite-A500] control_cb (./pm/pmiserv/pmiserv_cb.c:202): > assert (!closed) failed > [mpiexec@basma-Satellite-A500] HYDT_dmxu_poll_wait_for_event > (./tools/demux/demux_poll.c:77): callback returned error status > [mpiexec@basma-Satellite-A500] HYD_pmci_wait_for_completion > (./pm/pmiserv/pmiserv_pmci.c:197): error waiting for event > [mpiexec@basma-Satellite-A500] main (./ui/mpich/mpiexec.c:331): process > manager error waiting for completion > basma@basma-Satellite-A500:~$ > > > ________________________________ > Date: Sun, 19 May 2013 16:26:32 -0500 > From: correac2(a)illinois.edu > To: discuss(a)mpich.org > Subject: Re: [mpich-discuss] checkpoint error > > > > On May 19, 2013 4:02 PM, "basma a.azeem" <basmaabdelazeem(a)hotmail.com> > wrote: >> >> Thank you for your help >> >> i am using mpich-3.0.3 . with blcr-0.8.5 to checkpoint the integer Sort >> App of NPB, it give me the following error : >> >> >> basma@basma-Satellite-A500:~$ mpiexec -ckpointlib blcr -ckpoint-prefix >> /home/buntinas/ckpts/app.ckpoint -ckpoint-interval 1 -n 4 >> /home/basma/NPB3.3/NPB3.3/NPB3.3-MPI/bin/is.A.4 > It sounds like that path should be something like > /home/basma/ckpts/app.ckpoint instead. > >> >> >> NAS Parallel Benchmarks 3.3 -- IS Benchmark >> >> Size: 8388608 (class A) >> Iterations: 100 >> Number of processes: 4 >> >> iteration >> 1 >> 2 >> 3 >> 4 >> 5 >> 6 >> 7 >> 8 >> 9 >> 10 >> [proxy:0:0@basma-Satellite-A500] requesting checkpoint >> [proxy:0:0@basma-Satellite-A500] HYDT_ckpoint_checkpoint >> (./tools/ckpoint/ckpoint.c:106): Failed to stat checkpoint prefix >> "/home/buntinas/ckpts/app.ckpoint": No such file or directory >> [proxy:0:0@basma-Satellite-A500] HYD_pmcd_pmip_control_cmd_cb >> (./pm/pmiserv/pmip_cb.c:905): checkpoint suspend failed >> [proxy:0:0@basma-Satellite-A500] HYDT_dmxu_poll_wait_for_event >> (./tools/demux/demux_poll.c:77): callback returned error status >> [proxy:0:0@basma-Satellite-A500] main (./pm/pmiserv/pmip.c:206): demux >> engine error waiting for event >> [mpiexec@basma-Satellite-A500] control_cb (./pm/pmiserv/pmiserv_cb.c:202): >> assert (!closed) failed >> [mpiexec@basma-Satellite-A500] HYDT_dmxu_poll_wait_for_event >> (./tools/demux/demux_poll.c:77): callback returned error status >> [mpiexec@basma-Satellite-A500] HYD_pmci_wait_for_completion >> (./pm/pmiserv/pmiserv_pmci.c:197): error waiting for event >> [mpiexec@basma-Satellite-A500] main (./ui/mpich/mpiexec.c:331): process >> manager error waiting for completion >> basma@basma-Satellite-A500:~$ >> >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss > > > _______________________________________________ discuss mailing list > discuss(a)mpich.org To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Jeff Hammond Argonne Leadership Computing Facility University of Chicago Computation Institute jhammond(a)alcf.anl.gov / (630) 252-5381 http://www.linkedin.com/in/jeffhammond https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond ALCF docs: http://www.alcf.anl.gov/user-guides

1 0

Re: [mpich-discuss] checkpoint error
by Pavan Balaji 19 May '13

19 May '13

On 05/19/2013 04:33 PM US Central Time, basma a.azeem wrote: > "/home/basma/ckpts/app.ckpoint": No such file or directory FYI. -- Pavan Balaji http://www.mcs.anl.gov/~balaji

1 0

Re: [mpich-discuss] checkpoint error
by basma a.azeem 19 May '13

19 May '13

same error basma@basma-Satellite-A500:~$ mpiexec -ckpointlib blcr -ckpoint-prefix /home/basma/ckpts/app.ckpoint -ckpoint-interval 1 -n 4 /home/basma/NPB3.3/NPB3.3/NPB3.3-MPI/bin/is.A.4 NAS Parallel Benchmarks 3.3 -- IS Benchmark Size: 8388608 (class A) Iterations: 100 Number of processes: 4 iteration 1 2 3 4 5 6 7 8 9 10 11 [proxy:0:0@basma-Satellite-A500] requesting checkpoint [proxy:0:0@basma-Satellite-A500] HYDT_ckpoint_checkpoint (./tools/ckpoint/ckpoint.c:106): Failed to stat checkpoint prefix "/home/basma/ckpts/app.ckpoint": No such file or directory [proxy:0:0@basma-Satellite-A500] HYD_pmcd_pmip_control_cmd_cb (./pm/pmiserv/pmip_cb.c:905): checkpoint suspend failed [proxy:0:0@basma-Satellite-A500] HYDT_dmxu_poll_wait_for_event (./tools/demux/demux_poll.c:77): callback returned error status [proxy:0:0@basma-Satellite-A500] main (./pm/pmiserv/pmip.c:206): demux engine error waiting for event [mpiexec@basma-Satellite-A500] control_cb (./pm/pmiserv/pmiserv_cb.c:202): assert (!closed) failed [mpiexec@basma-Satellite-A500] HYDT_dmxu_poll_wait_for_event (./tools/demux/demux_poll.c:77): callback returned error status [mpiexec@basma-Satellite-A500] HYD_pmci_wait_for_completion (./pm/pmiserv/pmiserv_pmci.c:197): error waiting for event [mpiexec@basma-Satellite-A500] main (./ui/mpich/mpiexec.c:331): process manager error waiting for completion basma@basma-Satellite-A500:~$ Date: Sun, 19 May 2013 16:26:32 -0500 From: correac2(a)illinois.edu To: discuss(a)mpich.org Subject: Re: [mpich-discuss] checkpoint error On May 19, 2013 4:02 PM, "basma a.azeem" <basmaabdelazeem(a)hotmail.com> wrote: > > Thank you for your help > > i am using mpich-3.0.3 . with blcr-0.8.5 to checkpoint the integer Sort App of NPB, it give me the following error : > > > basma@basma-Satellite-A500:~$ mpiexec -ckpointlib blcr -ckpoint-prefix /home/buntinas/ckpts/app.ckpoint -ckpoint-interval 1 -n 4 /home/basma/NPB3.3/NPB3.3/NPB3.3-MPI/bin/is.A.4 It sounds like that path should be something like /home/basma/ckpts/app.ckpoint instead. > > > NAS Parallel Benchmarks 3.3 -- IS Benchmark > > Size: 8388608 (class A) > Iterations: 100 > Number of processes: 4 > > iteration > 1 > 2 > 3 > 4 > 5 > 6 > 7 > 8 > 9 > 10 > [proxy:0:0@basma-Satellite-A500] requesting checkpoint > [proxy:0:0@basma-Satellite-A500] HYDT_ckpoint_checkpoint (./tools/ckpoint/ckpoint.c:106): Failed to stat checkpoint prefix "/home/buntinas/ckpts/app.ckpoint": No such file or directory > [proxy:0:0@basma-Satellite-A500] HYD_pmcd_pmip_control_cmd_cb (./pm/pmiserv/pmip_cb.c:905): checkpoint suspend failed > [proxy:0:0@basma-Satellite-A500] HYDT_dmxu_poll_wait_for_event (./tools/demux/demux_poll.c:77): callback returned error status > [proxy:0:0@basma-Satellite-A500] main (./pm/pmiserv/pmip.c:206): demux engine error waiting for event > [mpiexec@basma-Satellite-A500] control_cb (./pm/pmiserv/pmiserv_cb.c:202): assert (!closed) failed > [mpiexec@basma-Satellite-A500] HYDT_dmxu_poll_wait_for_event (./tools/demux/demux_poll.c:77): callback returned error status > [mpiexec@basma-Satellite-A500] HYD_pmci_wait_for_completion (./pm/pmiserv/pmiserv_pmci.c:197): error waiting for event > [mpiexec@basma-Satellite-A500] main (./ui/mpich/mpiexec.c:331): process manager error waiting for completion > basma@basma-Satellite-A500:~$ > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] checkpoint error
by Ralf Gunter Correa Carvalho 19 May '13

19 May '13

On May 19, 2013 4:02 PM, "basma a.azeem" <basmaabdelazeem(a)hotmail.com> wrote: > > Thank you for your help > > i am using mpich-3.0.3 . with blcr-0.8.5 to checkpoint the integer Sort App of NPB, it give me the following error : > > > basma@basma-Satellite-A500:~$ mpiexec -ckpointlib blcr -ckpoint-prefix /home/buntinas/ckpts/app.ckpoint -ckpoint-interval 1 -n 4 /home/basma/NPB3.3/NPB3.3/NPB3.3-MPI/bin/is.A.4 It sounds like that path should be something like /home/basma/ckpts/app.ckpoint instead. > > > NAS Parallel Benchmarks 3.3 -- IS Benchmark > > Size: 8388608 (class A) > Iterations: 100 > Number of processes: 4 > > iteration > 1 > 2 > 3 > 4 > 5 > 6 > 7 > 8 > 9 > 10 > [proxy:0:0@basma-Satellite-A500] requesting checkpoint > [proxy:0:0@basma-Satellite-A500] HYDT_ckpoint_checkpoint (./tools/ckpoint/ckpoint.c:106): Failed to stat checkpoint prefix "/home/buntinas/ckpts/app.ckpoint": No such file or directory > [proxy:0:0@basma-Satellite-A500] HYD_pmcd_pmip_control_cmd_cb (./pm/pmiserv/pmip_cb.c:905): checkpoint suspend failed > [proxy:0:0@basma-Satellite-A500] HYDT_dmxu_poll_wait_for_event (./tools/demux/demux_poll.c:77): callback returned error status > [proxy:0:0@basma-Satellite-A500] main (./pm/pmiserv/pmip.c:206): demux engine error waiting for event > [mpiexec@basma-Satellite-A500] control_cb (./pm/pmiserv/pmiserv_cb.c:202): assert (!closed) failed > [mpiexec@basma-Satellite-A500] HYDT_dmxu_poll_wait_for_event (./tools/demux/demux_poll.c:77): callback returned error status > [mpiexec@basma-Satellite-A500] HYD_pmci_wait_for_completion (./pm/pmiserv/pmiserv_pmci.c:197): error waiting for event > [mpiexec@basma-Satellite-A500] main (./ui/mpich/mpiexec.c:331): process manager error waiting for completion > basma@basma-Satellite-A500:~$ > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss

1 0

checkpoint error
by basma a.azeem 19 May '13

19 May '13

Thank you for your help i am using mpich-3.0.3 . with blcr-0.8.5 to checkpoint the integer Sort App of NPB, it give me the following error : basma@basma-Satellite-A500:~$ mpiexec -ckpointlib blcr -ckpoint-prefix /home/buntinas/ckpts/app.ckpoint -ckpoint-interval 1 -n 4 /home/basma/NPB3.3/NPB3.3/NPB3.3-MPI/bin/is.A.4 NAS Parallel Benchmarks 3.3 -- IS Benchmark Size: 8388608 (class A) Iterations: 100 Number of processes: 4 iteration 1 2 3 4 5 6 7 8 9 10 [proxy:0:0@basma-Satellite-A500] requesting checkpoint [proxy:0:0@basma-Satellite-A500] HYDT_ckpoint_checkpoint (./tools/ckpoint/ckpoint.c:106): Failed to stat checkpoint prefix "/home/buntinas/ckpts/app.ckpoint": No such file or directory [proxy:0:0@basma-Satellite-A500] HYD_pmcd_pmip_control_cmd_cb (./pm/pmiserv/pmip_cb.c:905): checkpoint suspend failed [proxy:0:0@basma-Satellite-A500] HYDT_dmxu_poll_wait_for_event (./tools/demux/demux_poll.c:77): callback returned error status [proxy:0:0@basma-Satellite-A500] main (./pm/pmiserv/pmip.c:206): demux engine error waiting for event [mpiexec@basma-Satellite-A500] control_cb (./pm/pmiserv/pmiserv_cb.c:202): assert (!closed) failed [mpiexec@basma-Satellite-A500] HYDT_dmxu_poll_wait_for_event (./tools/demux/demux_poll.c:77): callback returned error status [mpiexec@basma-Satellite-A500] HYD_pmci_wait_for_completion (./pm/pmiserv/pmiserv_pmci.c:197): error waiting for event [mpiexec@basma-Satellite-A500] main (./ui/mpich/mpiexec.c:331): process manager error waiting for completion basma@basma-Satellite-A500:~$

1 0