Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

Subject: Re: [OMPI devel] ompi_info
From: George Bosilca (bosilca_at_[hidden])
Date: 2013-07-18 11:50:40

On Jul 18, 2013, at 17:07 , Nathan Hjelm <hjelmn_at_[hidden]> wrote:

> This was discussed in depth before the MCA rewrite came into the trunk. There are only two cases where we load and register all the available components: ompi_info, and MPI_T_init_thread(). The normal MPI case does not have this behavior and instead loads only the requested components.

How is this part of the code validated? It might capitalize on some type of "trust". Unfortunately … I have no such notion.

I would rather take the path of the "least astonishment", a __consistent__ behavior where we always abide to the configuration files (user level as well as system level). If you want to see every single parameter possibly available to you (based on your rights of course), temporary remove the configuration file. Or we can provide a specific ompi_info option to ignore the configuration files, but not make this the default.