Open MPI logo

Hardware Locality Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [hwloc-devel] multinode/network topology status
From: Samuel Thibault (samuel.thibault_at_[hidden])
Date: 2011-10-04 10:51:34


Brice Goglin, le Wed 21 Sep 2011 08:54:52 +0200, a écrit :
> Example of C interface use (assembling 3 nodes in a global topology with
> 3 levels of switches):
> C interface doc:
> Manpages of the command-line tools (with examples at the end):
> General doc about all this:

This looks good. hwloc-assembler-remote should probably have a
--lstopo-path option to specify where to find lstopo, since the host
from which we run it may not have the same hwloc installation as the
target nodes. I'm actually unsure whether it really should default to
$bindir/lstopo and not simply to lstopo.

There is an issue with the distance code that appears when there are
several machines with NUMA distances: the distance code assumes that the
root of the topology has cpusets to be compared with, and quickly
crashes on insert_by_cpuset or get_obj_covering_cpuset calls.