Keep in mind that -- in general -- Open MPI has two different kinds of traffic:
1. "Out of band" (OOB) traffic, used for launching/monitoring/killing the job
2. MPI traffic
The OOB traffic generally uses TCP, and can be over whatever network you want.
The MPI traffic you generally want to use yo
Keep in mind that -- in general -- Open MPI has two different kinds of traffic:
1. "Out of band" (OOB) traffic, used for launching/monitoring/killing the job
2. MPI traffic
The OOB traffic generally uses TCP, and can be over whatever network you want.
The MPI traffic you generally want to use yo
Keep in mind that -- in general -- Open MPI has two different kinds of traffic:
1. "Out of band" (OOB) traffic, used for launching/monitoring/killing the job
2. MPI traffic
The OOB traffic generally uses TCP, and can be over whatever network you want.
The MPI traffic you generally want to use yo
Thanks for the tests !
What was fixed in openmpi is handling disconnected infinipath port.
Restoring signal handlers when libinfinipath.so is unloaded (when
mca_mtl_psm.so is unloaded from our point of view) can only be fixed within
libinfinipath.so. It might have already been fixed in the latest
Thanks for the tests !
What was fixed in openmpi is handling disconnected infinipath port.
Restoring signal handlers when libinfinipath.so is unloaded (when
mca_mtl_psm.so is unloaded from our point of view) can only be fixed within
libinfinipath.so.
It might have already been fixed in the late
If you configure with --disable-dlopen, then libinfinipath.so is slurped
and hence the infinipath signal handler is always set, even if you disable
the psm mtl or choose to only use the ob1 pml.
if you do not configure with --disable-dlopen, then the infinipath signal
handler is set when mca_mtl_
If you configure with --disable-dlopen, then libinfinipath.so is slurped
and hence the infinipath signal handler is always set, even if you
disable the psm mtl or choose to only use the ob1 pml.
if you do not configure with --disable-dlopen, then the infinipath
signal handler is set when mca_m
Hello Gilles
I am not sure if I understand you correctly, but let me answer based on
what I think you mean:
the infinipath signal handler only dump the stack (into a .btr file, yeah !)
so if your application crashes without it, you should examine the core
file and see what is going wrong.
If t
Durga,
the infinipath signal handler only dump the stack (into a .btr file, yeah !)
so if your application crashes without it, you should examine the core
file and see what is going wrong.
note the infinipath signal handler is set in the constructor of
libinfinipath.so,
and used *not* to be remov
