This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
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*
(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 =>