I'm getting the hwloc-1.7 version of the python bindings ready to go. I've
tried to add GL, Intel MIC, NVML, and CUDA support.
I can't implement much of CUDA or NVML for lack of python bindings for those
libraries, but I did what I could.
I can't test any of these for lack of hardware. If you have
Brice Goglin, le Mon 03 Jun 2013 19:50:26 +0200, a écrit :
> Le 03/06/2013 10:52, Samuel Thibault a écrit :
> > Brice Goglin, le Mon 03 Jun 2013 10:46:49 +0200, a écrit :
> >> hwloc/bitmap.h is the biggest problem, plugins should be allowed to use
> >> all of them but there are many of them. Sp
Le 03/06/2013 10:52, Samuel Thibault a écrit :
> Brice Goglin, le Mon 03 Jun 2013 10:46:49 +0200, a écrit :
>> hwloc/bitmap.h is the biggest problem, plugins should be allowed to use
>> all of them but there are many of them. Splitting hwloc-bitmap.so
>> out of hwloc.so would be an easy way to
Brice Goglin, le Mon 03 Jun 2013 10:46:49 +0200, a écrit :
> hwloc/bitmap.h is the biggest problem, plugins should be allowed to use
> all of them but there are many of them. Splitting hwloc-bitmap.so
> out of hwloc.so would be an easy way to solve this. The bitmap API is
> totally independent
Hello,
I recently got the first report of what we knew would happen one day or
another: plugin namespace issues caused by somebody loading a
plugin-enabled hwloc as a plugin. It comes from OpenCL (which uses
plugins to select implementations) because one implementation depends on
hwloc. What happe