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] v1.7
From: Samuel Thibault (samuel.thibault_at_[hidden])
Date: 2013-01-07 13:27:04

Jeff Squyres (jsquyres), le Mon 07 Jan 2013 19:19:15 +0100, a écrit :
> On Jan 7, 2013, at 12:59 PM, Samuel Thibault <samuel.thibault_at_[hidden]>
> > Because I may not know *everything* that I want. Who knows what
> > proprietary plugin I need to use to discover CPUs, while I know that for
> > GPUs I can use cuda, but I don't want to use nvml.
> >
> >> Taking your example: HWLOC_COMPONENTS=foo,^bar,^baz,yow
> >> Is the same as: HWLOC_COMPONENTS=foo,yow
> >
> > No, because there is also the implicit "and the default plugins" after
> > that.
> So you're really saying "not bar and baz, but I do want everything else."

I'm also saying "foo and yow before everything else", which as Brice
mentioned, does matter.

> - if foo doesn't load / isn't used, it's an error
> - don't load bar
> - don't load baz
> - if yow doesn't load / isn't used, it's an error
> - try to load all other components, but don't warn/error if they don't load / aren't used

We don't imply erroring out. Components never error out, they just don't
discover anything :)

What we however have is the ordering.