ost you were talking about), and it made the core
hwloc code much more complex.
Thanks for the report
Brice
Le 05/02/2018 à 23:02, Madhu, Kavitha Tiptur a écrit :
Hi
I have a question on topology query. The hwloc 2.0.0 documentation states that
"Additionally it may assemble the topol
Hi
I have a question on topology query. The hwloc 2.0.0 documentation states that
"Additionally it may assemble the topologies of multiple machines into a single
one so as to let applications consult the topology of an entire fabric or
cluster at once.”. Since “system” object type has been
A follow up question, can the call to hwloc_get_non_io_ancestor_obj() return a
numa object?
> On Mar 14, 2018, at 3:09 PM, Madhu, Kavitha Tiptur <kma...@anl.gov> wrote:
>
> Hi
> This function was used to query depth of hardware objects of a certain type
> to bind
l(obj->type)) obj = obj->parent;
>
> I'll update the doc too. Thanks.
>
> Brice
>
>
>
> Le 14/03/2018 à 22:16, Madhu, Kavitha Tiptur a écrit :
>> A follow up question, can the call to hwloc_get_non_io_ancestor_obj() return
>> a numa object?
>>
Hello folks,
The function hwloc_get_type_or_above_depth() is supposed to return the depth of
objects of type “type" or above. It internally calls hwloc_get_type_depth which
returns virtual depths to NUMA, IO and misc objects. In order to retrieve the
actual depth of these objects, one needs to
ch sense
> in the general case.
>
> What do you use this function for? I thought of removing it from 2.0
> because it's hard to define a "usual" order for object types (for
> instance L3 can be above or below NUMA for different modern platforms).
>
> Brice
>
>
>
e we already invested a
>>> lot of effort to migrate to hwloc-2.x.
>>>
>>> — Pavan
>>>
>>> Sent from my iPhone
>>>
>>>> On Apr 3, 2018, at 6:19 PM, Brice Goglin <brice.gog...@inria.fr> wrote:
>>>>
>>
>>
>> — I tried building older netloc with hwloc 2.0 and it throws compiler
>> errors. Note that netloc was cloned from it’s git repo.
>
> My guess is that the "map" part that joins netloc's info about the
> fabric with hwloc's info about the nodes doesn't like hwloc 2.0. But
> that should be
s' internals). We didn't want to expose such a large API before
> getting actual user feedback.
>
> In short, in your need features, please let us know, so that we can
> discuss what to expose in the public headers and how.
>
> Brice
>
>
>
>
> Le 30/03/201
We will upgrade the hwloc submodule used in MPICH asap. IIRC, we have supressed
hwloc warnings as well. I will double check this.
Kavitha
On Sep 14, 2018, at 12:36 AM, Brice Goglin
mailto:brice.gog...@inria.fr>> wrote:
If lstopo fails there, run "hwloc-gather-topology foo" and send
10 matches
Mail list logo