Re: [hwloc-devel] [RFC] applying native OS restrictions to XML imported topology

> On Oct 21, 2016, at 10:09 AM, Brice Goglin wrote: > > Le 21/10/2016 17:21, r...@open-mpi.org a écrit : >> I should add: this does beg the question of how a proc “discovers” its >> resource constraints without having access to the hwloc tree.

Re: [hwloc-devel] [RFC] applying native OS restrictions to XML imported topology

Le 21/10/2016 17:21, r...@open-mpi.org a écrit : > I should add: this does beg the question of how a proc “discovers” its > resource constraints without having access to the hwloc tree. One possible > solution - the RM already knows the restrictions, and so it could pass those > down at proc

Re: [hwloc-devel] [RFC] applying native OS restrictions to XML imported topology

I should add: this does beg the question of how a proc “discovers” its resource constraints without having access to the hwloc tree. One possible solution - the RM already knows the restrictions, and so it could pass those down at proc startup (e.g., as part of the PMIx info). We could pass

Re: [hwloc-devel] [RFC] applying native OS restrictions to XML imported topology

Hmmm...I think maybe we are only seeing a small portion of the picture here. There are two pieces of the problem when looking at large SMPs: * time required for discovery - your proposal is attempting to address that, assuming that the RM daemon collects the topology and then communicates it to

[hwloc-devel] [RFC] applying native OS restrictions to XML imported topology

Hello Based on recent discussion about hwloc_topology_load() being slow on some "large" platforms (almost 1 second on KNL), here's a new feature proposal: We've been recommending the use of XML to avoid multiple expensive discovery: Export to XML once at boot, and reload from XML for each actual