Brice Goglin, le Wed 22 Aug 2012 07:52:07 +0200, a écrit :
> Le 21/08/2012 21:18, Samuel Thibault a écrit :
> > 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 req
Le 21/08/2012 21:18, Samuel Thibault a écrit :
> 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 simult
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
I implemented most of this in the component branch. The changes in the
core look heavy but it's not too bad in the end.
Now, each old backend registers a "component" that can be instantiated
into a "backend" structure depending on the topology configuration. By
default, you get your OS backend an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/08/12 19:02, Brice Goglin wrote:
> Aside from the main "discover" callback, backends may also define
> some callbacks to be invoked when new object are created. The main
> example is Linux creating "OS devices" when a new "PCI device" is
> added
Brice Goglin, le Tue 07 Aug 2012 13:29:31 +0200, a écrit :
> Le 07/08/2012 13:06, Jeff Squyres a écrit :
> >> Aside from the main "discover" callback, backends may also define some
> >> callbacks to be invoked when new object are created. The main example is
> >> Linux creating "OS devices" when a
Le 07/08/2012 13:06, Jeff Squyres a écrit :
>> Aside from the main "discover" callback, backends may also define some
>> callbacks to be invoked when new object are created. The main example is
>> Linux creating "OS devices" when a new "PCI device" is added by the PCI
>> backend. CUDA could use tha
On Aug 7, 2012, at 5:02 AM, Brice Goglin wrote:
> Antoine Rougier finished his internship recently so here's a summary of
> what he did in the "backends" branch. For the record, the goal of his
> work was to explore how to change our backends into proper plugins so
> that we can easily avoid hard
Antoine Rougier finished his internship recently so here's a summary of
what he did in the "backends" branch. For the record, the goal of his
work was to explore how to change our backends into proper plugins so
that we can easily avoid hard dependencies between the hwloc core and
external librarie
