Open MPI logo

Hardware Locality Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

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.

Subject: Re: [hwloc-devel] Priority of env vars vs. application options
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2009-10-28 09:26:03

On Oct 28, 2009, at 9:21 AM, Samuel Thibault wrote:

> > - command line
> > - env variable
> > - compiled-in defaults
> >
> > If you're in an environment where you can't pass command line
> options,
> > then use the environment (either explicitly set or unset it).
> But what about the situation that Brice suggested, i.e. the
> application
> itself using xml files internally? Where in the list should that be?

Can you pass XML filenames via the API?

I would think that the API *only* looks at the names passed as
parameters -- command line, env variable, etc. are upper-layer
abstractions added by top-level tools like lstopo, etc.

Jeff Squyres