Open MPI logo

Hardware Locality Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Hardware Locality Development mailing list

Subject: Re: [hwloc-devel] backends and plugins
From: Samuel Thibault (samuel.thibault_at_[hidden])
Date: 2012-08-21 15:18:22

Brice Goglin, le Tue 21 Aug 2012 18:49:48 +0200, a écrit :
> 1) We load plugins and list existing components once per topology. We
> should do it only once per process. But that requires some locking in
> case multiple topologies are loaded simultaneously, which means we need
> thread-safety. Do we want pthread_mutex() for this?

I'd say so. We can test in whether -lpthread is really
needed for that (it is not on most systems, which optimizes things away
in non-libpthread cases).

> 2) Some internal functions are now exported to plugins. Do we want a
> special namespace? "hwloc__" instead of "hwloc_"? Is there anyway to
> make them visibile to plugins but not to applications?

Not that I know of.

> 3) I currently use the system libltdl. People usually ask libtool to
> copy it's libtldl implementation inside the project source at autogen to
> make sure it's compatible/working. So we won't have libltdl in SVN,
> we'll have it in tarballs, and we'll build it (with a sub-configure) if
> plugins are enabled. Is anybody against this?

It looks fine to me.