thanks, --Guy
I was considering the design of an administration tool in python, and my
original idea was to have each module that needs the topology object create
its own. This means that different parts of the same program (but possibly in
different threads) would call init and load on their own topology structure,
and use that structure in their hwloc routines calls.
Is this a safe/reasonable/efficient way to go, or should I call init and load
on only one structure and pass that one around throughout the application?
- [hwloc-devel] multiple simultaneous topology inits? Guy Streeter
- Re: [hwloc-devel] multiple simultaneous topology init... Jeff Squyres
- Re: [hwloc-devel] multiple simultaneous topology ... Brice Goglin
- Re: [hwloc-devel] multiple simultaneous topol... Bernd Kallies
- Re: [hwloc-devel] multiple simultaneous t... Brice Goglin
- Re: [hwloc-devel] multiple simultane... Bernd Kallies
- [hwloc-devel] restrict branch Brice Goglin
- Re: [hwloc-devel] restrict branc... Brice Goglin
- Re: [hwloc-devel] restrict and P... Samuel Thibault
- Re: [hwloc-devel] restrict a... Brice Goglin
- [hwloc-devel] Merging the PC... Brice Goglin