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] merging plugins?
From: Brice Goglin (Brice.Goglin_at_[hidden])
Date: 2012-09-25 04:34:04

Le 25/09/2012 10:17, Brice Goglin a écrit :
> Le 25/09/2012 09:49, Samuel Thibault a écrit :
>> One thing which can be confusing for the user is that core_linux goes
>> to the core os list while core_libpci goes to the additional list. It
>> would probably be better to use a different class name. I actually don't
>> currently understand what classes are used for.
> The class name was initially used to distinguish between normal (core)
> plugins and xml backends. It may be possible to completely remove it now
> that component struct have a type, I'll check.
> We have the "core_xml" component (generic xml support) and "xml_libxml"
> + "xml_nolibxml" backends behind that. I am fine with removing the
> "core_" prefix,

I am also going to add a hwloc_ prefix to plugin filenames because we
obviously can't create a (libtool even warns about this).
XML backends could be hwlocxml_ (not hwloc_xml_) to make it clear that
they are not normal hwloc_ plugins.