Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

Subject: Re: [OMPI devel] [devel-core] OMPI MCA components - track external libs versions
From: Mike Dubman (miked_at_[hidden])
Date: 2014-04-14 16:05:37


hmm... very smart. thanks. seems it can work. will think about it more.

On Mon, Apr 14, 2014 at 10:13 PM, Jeff Squyres (jsquyres) <
jsquyres_at_[hidden]> wrote:

> On Apr 14, 2014, at 2:57 PM, Mike Dubman <miked_at_[hidden]> wrote:
>
> > I think (+know) that many production environments and OMPI users will be
> happy to have it.
>
> Agreed. Something like:
>
> char version_str[128];
>
> snprintf(version_str, sizeof(version_str),
> "%d.%d.%d", libusnic_major, libusnic_minor, libusnic_release);
>
> mca_base_component_var_register(&mca_btl_usnic_component.super.btl_version,
> "libusnic_version",
> "Version of the libusnic library",
> MCA_BASE_VAR_TYPE_STRING,
> NULL, 0, 0,
> OPAL_INFO_LVL_3,
> MCA_BASE_VAR_SCOPE_READONLY,
> version_str);
>
> Then:
>
> shell$ ompi_info --param btl usnic --level 9 --parsable | grep version |
> grep :value:
> mca:btl:usnic:param:btl_usnic_libusnic_version:value:1.2.3
>
> Make sense?
>
> I suggest level 2 or level 3 for such vars. They shouldn't be in default
> level 1 ompi_info output, but it is information that may be required to run
> correctly, so it should be in the "end user" set of info (i.e., be <= 3).
> See https://svn.open-mpi.org/trac/ompi/wiki/MCAParamLevels.
>
> My point: I don't think you need any new infrastructure for this -- you
> can do it today.
>
> --
> Jeff Squyres
> jsquyres_at_[hidden]
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
>
> _______________________________________________
> devel mailing list
> devel_at_[hidden]
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/04/14517.php
>