Jeff Squyres wrote:
>> I am not sure. The object structure contains a father pointer. We use
>> parent in the API, but it might refer to different things, like father,
>> grandfather, ...
>>
>
> FWIW, the english word "parent" definitely refers to the immediate ancestor.
> It does *not*
Brice Goglin wrote:
> Hello,
>
> While cleaning the System/Machine root types, I wondered what we
> actually want to store in memory_kB attributes. It looks obvious for
> Caches and NUMA nodes. But I am not sure about Machines and Systems.
>
> If we have a machine with 2 NUMA nodes, should the
Perhaps we should distinguish between memory in this object and memory that is
accessible by this object...?
I.e., cache and numa node can have x local memory. System/machine may have 0
local memory but (sum of children) accessible memory.
Specifically:
1 I think it is a common enough action
Just so I understand - are you saying hwloc should track both the total amount
of memory *and* the makeup of that amount, broken up by page size? So obj A
may have x total memory, split across y 4k pages and z bigk hugepages (for
example)? And then the question becomes how to store this
Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.0a1r1649
Start time: Sat Jan 16 21:01:04 EST 2010
End time: Sat Jan 16 21:03:11 EST 2010
Your friendly daemon,
Cyrador
