On Nov 4, 2014, at 9:10 AM, Brice Goglin wrote:
>> - pu_children
>> - io_children
>> - misc_children
>
> OK but what does "pe" stand for? did you mean "pu" to match our PU objects?
I said "pu_children". Really. I didn't edit the text above and make it look
like I
Le 04/11/2014 14:59, Jeff Squyres (jsquyres) a écrit :
> If you're going to separate them from the normal "children", then how about
> naming them for what they are? E.g.:
>
> - pe_children
> - io_children
> - misc_children
OK but what does "pe" stand for? did you mean "pu" to match our PU
On Nov 3, 2014, at 5:49 AM, Brice Goglin wrote:
> * don't put I/O objects in "normal" children since it confuses programs
> consulting the children list. rather place them under a dedicated child
> pointer special objects such as Misc may go there as well.
If you're going
Brice Goglin, le Mon 03 Nov 2014 11:49:02 +0100, a écrit :
> * kerrighed support (single-system image): planned for removal since
> 2012, see https://github.com/open-mpi/hwloc/issues/73
Right, Kerrighed is mostly discontinued.
> I am also considering this change that shouldn't break existing
Hello
I am considering removing some features from hwloc since the next major
release will be called 2.0 and it deserves major changes :)
If you care about anything below, please speak up:
* the "custom" interface and hwloc-assembler tools (for assembling the
topology of multiple nodes): nobody