We seem to have gotten into a state again of generating a ton of warnings on
master - can folks take a look at these and clean them up?
opal_datatype_pack.c: In function ‘pack_predefined_heterogeneous’:
opal_datatype_pack.c:421:24: warning: variable ‘_l_blength’ set but not used
[-Wunused-but-se
Ralph,
Bringing back the coll/sync is a cheap shot at hiding a real issue behind a
smoke curtain. As Nathan described in his email, Open MPI lacks of control
flow on eager messages is the real culprit here, and the loop around any
one-to-many collective (bcast and scatter*) was only helping to exa
I don’t disagree with anything you said - however, this problem has been
reported in our library for more than a decade (goes way back into the old Trac
days), and has yet to be resolved. Meantime, we have a user that is “down” and
needs a solution. Whether it is a “cheap shot” or not is irrelev
Ralph,
in the meantime, and if not done already, your user can simply redefine
MPI_Bcast in the app.
int MPI_Bcast(void *buffer, int count, MPI_Datatype type, int root,
MPI_Comm comm) {
PMPI_Barrier(comm);
return PMPI_Bcast(buffer, count, datatype, root, comm);
}
the root causes are
- n
As I said earlier, modifying these legacy apps is not a desirable solution. The
coll/sync component was developed specifically to alleviate these problems in
an acceptable manner, albeit not optimal. Performance, in this case, is
secondary to just getting the app to run.
> On Aug 20, 2016, at
I got your point, I was just pointing to an other option "in the meantime".
fwiw, the bits of code I posted earlier can be put in a shared library that
is LD_PRELOAD'ed,
so the application is kept unmodified.
Cheers,
Gilles
On Sunday, August 21, 2016, r...@open-mpi.org wrote:
> As I said earl
