Actually, the compromise was listed in my original mail: 2a. Fair enough. The long-standing ompi_info behavior precedent alone is probably enough to warrant re-thinking the new ompi_info behavior. Nathan will implement a compromise (that George was ok with when I talked on the phone with him). If you have a <framework> parameter somewhere that disables components (e.g., $HOME/.openmpi-mca-params.conf contains "btl = tcp,sm,self"), then ompi_info will somehow mark those components' parameters as "inactive" in the prettyprint and parseable outputs
On Aug 28, 2013, at 2:50 AM, George Bosilca <bosi...@icl.utk.edu> wrote: > Jeff is indeed correct, the compromise we reached was to default to the > historical behavior of showing only the parameters of selected components and > have an option to show everything else. > > George. > > PS: Shouldn't "ompi_info --param all all" be identical to "ompi_info --all"? > > On Aug 27, 2013, at 22:10 , Jeff Squyres (jsquyres) <jsquy...@cisco.com> > wrote: > >> On Aug 27, 2013, at 3:13 PM, Nathan Hjelm <hje...@lanl.gov> wrote: >> >>>>> 1a. ompi_info has a *very long-standing precedent* behavior of using >>>>> <framework> MCA params to exclude the display of components (and their >>>>> params). Users have come to rely on this behavior to test that OMPI is >>>>> honoring their $HOME/.openmpi-mca-params.conf file (for example) because >>>>> -- at least prior to new ompi_info -- there was no other way to verify >>>>> that. >>> >>> Please take a look @ r29070. I changed the default behavior of ompi_info >>> -a when --level is not specified to assume level 9. I also added an >>> option (--selected-only/-s) that limits the output to components that >>> may be selected. Let me know if this fix is ok. >> >> >> I don't think it's going to be enough. >> >> George's point is that the *default behavior* for ompi_info for years has >> been to do what --selected-only does. So adding a non-default option to get >> that same behavior... I think George will hate that. Right, George? :-) >> >> I think your option 2b) from your previous mail was the compromise: >> >> ----- >> To summarize what will be done: >> >> 1) --all without a --level will assume --level 9 >> 2) Either a) add an option to ompi_info to suppress registering all >> components when a component selection parameter is set (ie. --mca btl >> self,sm) or b) somehow mark the parameters of unused components as such. >> ----- >> >> I.e., show all components, but mark those who are not selected somehow. >> >> Sorry. :-\ >> >> -- >> Jeff Squyres >> jsquy...@cisco.com >> For corporate legal information go to: >> http://www.cisco.com/web/about/doing_business/legal/cri/ >> >> _______________________________________________ >> devel mailing list >> de...@open-mpi.org >> http://www.open-mpi.org/mailman/listinfo.cgi/devel > > _______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
