I'm a little unclear on this comment.
DMTCP currently supports checkpointing and restoring sockets over TCP, and we
are actively working on Infiniband support. However, we feel that value is
added by also working as an Open MPI module, where Open MPI handles all of the
network communication,
Thanks Alex. Can you answer George's other question about "hand waving"?
On Oct 7, 2011, at 3:59 PM, Alex Brick wrote:
> Yes, we were trying to give some background on the project and use consistent
> branding. Our package is called DMTCP, which includes two components: DMTCP
> (a
The test for the __may_alias_ attribute uses the following short code
snippet:
int * p_value __attribute__ ((__may_alias__));
int
main ()
{
;
return 0;
}
Indeed, for Intel 2011 compilers prior to 2011.6.233, this results in
a warning:
root@hydra openmpi-1.4.3]# module load
Yes, we were trying to give some background on the project and use consistent
branding. Our package is called DMTCP, which includes two components: DMTCP
(a distributed checkpointer), and MTCP (a single process checkpointer, which
can be used both standalone and internally by DMTCP).
This
Way too much hands waving here.
When you say certain networks you mean TCP and potentially SM. However, I doubt
even TCP can be fully supported. Not without the preconnect option … or a mean
to update the modes information.
george.
On Oct 7, 2011, at 14:56 , Josh Hursey wrote:
>> From what
>From what I have seen during development, this RFC integrates the MTCP
single process checkpointer into the C/R infrastructure of Open MPI.
The MTCP component of the DMTCP project can be used in insolation,
which is what they are integrating. So they can use DMTCP to
checkpoint/restart an
I ran into a problem this past week trying to upgrade our OpenMPI
1.4.3 for the latest Intel 2011 compiler, 2011.6.233.
make check fails with Segmentation Fault errors:
[root@hydra openmpi-1.4.3]# tail -20 ../openmpi-1.4.3-check-intel.
6.233.log
/bin/sh ../../libtool --tag=CC --mode=link
