Daniel,
thanks for the logs.
an other workaround is to
mpirun --mca coll ^hcoll ...
i was able to reproduce the issue, and it surprisingly occurs only if
the coll_ml module is loaded *before* the hcoll module.
/* this is not the case on my system, so i had to hack my
mca_base_component_path i
Gilles,
Attached the two output logs.
Thanks,
Daniel
On 06/22/2015 08:08 AM, Gilles Gouaillardet wrote:
Daniel,
i double checked this and i cannot make any sense with these logs.
if coll_ml_priority is zero, then i do not any way how
ml_coll_hier_barrier_setup can be invoked.
could you pl
Daniel,
i double checked this and i cannot make any sense with these logs.
if coll_ml_priority is zero, then i do not any way how
ml_coll_hier_barrier_setup can be invoked.
could you please run again with --mca coll_base_verbose 100
with and without --mca coll ^ml
Cheers,
Gilles
On 6/22/20
Daniel,
ok, thanks
it seems that even if priority is zero, some code gets executed
I will confirm this tomorrow and send you a patch to work around the issue
if that if my guess is proven right
Cheers,
Gilles
On Sunday, June 21, 2015, Daniel Letai wrote:
> MCA coll: parameter "coll_ml_prior
MCA coll: parameter "coll_ml_priority" (current value: "0", data source:
default, level: 9 dev/all, type: int)
Not sure how to read this, but for any n>1 mpirun only works with --mca
coll ^ml
Thanks for helping
On 06/18/2015 04:36 PM, Gilles Gouaillardet wrote:
This is really odd...
you ca
Thanks, will try it on Sunday (won't have access to the system till then)
On 06/18/2015 04:36 PM, Gilles Gouaillardet wrote:
This is really odd...
you can run
ompi_info --all
and search coll_ml_priority
it will display the current value and the origin
(e.g. default, system wide config, user co
This is really odd...
you can run
ompi_info --all
and search coll_ml_priority
it will display the current value and the origin
(e.g. default, system wide config, user config, cli, environment variable)
Cheers,
Gilles
On Thursday, June 18, 2015, Daniel Letai wrote:
> No, that's the issue.
>
No, that's the issue.
I had to disable it to get things working.
That's why I included my config settings - I couldn't figure out which
option enabled it, so I could remove it from the configuration...
On 06/18/2015 02:43 PM, Gilles Gouaillardet wrote:
Daniel,
ML module is not ready for prod
Daniel,
ML module is not ready for production and is disabled by default.
Did you explicitly enable this module ?
If yes, I encourage you to disable it
Cheers,
Gilles
On Thursday, June 18, 2015, Daniel Letai wrote:
> given a simple hello.c:
>
> #include
> #include
>
> int main(int argc, ch
given a simple hello.c:
#include
#include
int main(int argc, char* argv[])
{
int size, rank, len;
char name[MPI_MAX_PROCESSOR_NAME];
MPI_Init(&argc, &argv);
MPI_Comm_size(MPI_COMM_WORLD, &size);
MPI_Comm_rank(MPI_COMM_WORLD, &rank);
MPI_Get_proc
10 matches
Mail list logo
