Sorry, I accidentally pressed 'Send' before I was done writing the last
mail. What I wanted to ask was what is the parameter mpi_add_procs_cutoff
and why adding it seems to make a difference in the code path but not in
the end result of the program? How would it help me debug my problem?
Thank you
Hello Gilles
Setting -mca mpi_add_procs_cutoff 1024 indeed makes a difference to the
output, as follows:
With -mca mpi_add_procs_cutoff 1024:
reachable = 0x1
(Note that add_procs was called once and the value of 'reachable is
correct')
Without -mca mpi_add_procs_cutoff 1024
reachable = 0
At first glance, that seems a bit odd...
are you sure you correctly print the reachable bitmap ?
I would suggest you add some instrumentation to understand what happens
(e.g., printf before opal_bitmap_set_bit() and other places that prevent
this from happening)
one more thing ...
now, master defa
Hello Gilles
Thanks for jumping in to help again. Actually, I had already tried some of
your suggestions before asking for help.
I have several interconnects that can run both openib and tcp BTL. To
simplify things, I explicitly mentioned TCP:
mpirun -np 2 -hostfile ~/hostfile -mca pml ob1 -mca
did you check the add_procs callbacks ?
(e.g. mca_btl_tcp_add_procs() for the tcp btl)
this is where the reachable bitmap is set, and I guess this is what you are
looking for.
keep in mind that if several btl can be used, the one with the higher
exclusivity is used
(e.g. tcp is never used if openi
