Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

From: Rolf.Vandevaart_at_[hidden]
Date: 2007-10-02 09:43:48

I propose that we drop the mca parameter "btl_base_debug". It is an added
level of complexity that does not provide any benefit. In fact, the
code in the btl_base_open.c is such that we can never turn on verbose

A quick research of the other base components in the OMPI area show that
of them have a *_base_debug mca parameter. They only have a *_base_verbose

I will plan on making this change but just thought I would check and see if
there is some historical or other reason why btl_base_debug should *not*
be removed.
(This came up as I was trying to figure out how to turn on verbosity for
the MX problem reported on the users list. )


 burl-ct-v440-0 141 =>ompi_info -all | egrep
                MCA coll: parameter "coll_base_verbose" (current value: "0")
               MCA mpool: parameter "mpool_base_verbose" (current value:
                 MCA pml: parameter "pml_base_verbose" (current value: "0")
                 MCA bml: parameter "bml_base_verbose" (current value: "0")
                 MCA btl: parameter "btl_base_verbose" (current value: "0")
 burl-ct-v440-0 142 =>ompi_info -all | egrep
                 MCA btl: parameter "btl_base_debug" (current value: "0")
                          If btl_base_debug is 1 standard debug is
output, if > 1 verbose debug is output
 burl-ct-v440-0 143 =>