>
> The ACPI SLIT table (reported by numactl -H) was indeed often dumb or even
> wrong. But SLIT wasn't widely used anyway, so vendors didn't care much
> about putting valid info there, it didn't break anything in most
> applications. Hopefully it won't be the case for HMAT because HMAT will be
>
Le 01/10/2020 à 22:17, Jirka Hladky a écrit :
>
> This is interesting! ACPI tables are often wrong - having the option
> to annotate more accurate data to the hwloc is great.
The ACPI SLIT table (reported by numactl -H) was indeed often dumb or
even wrong. But SLIT wasn't widely used anyway, so
Hi Brice,
thanks for the quick reply! I was able to get access to one KNL server and
I have tested it there. It works - bandwidth is annotated and reported:-)
See [1]
It's also possible to add memory attribute using the C API or with
> hwloc-annotate to modify a XML
This is interesting! ACPI
Le 01/10/2020 à 19:16, Jirka Hladky a écrit :
> Hi Brice,
>
> this new feature sounds very interesting!
>
> Add hwloc/memattrs.h for exposing latency/bandwidth information
> between initiators (CPU sets for now) and target NUMA nodes,
> typically on heterogeneous platforms.
>
Hi Brice,
this new feature sounds very interesting!
Add hwloc/memattrs.h for exposing latency/bandwidth information
> between initiators (CPU sets for now) and target NUMA nodes,
> typically on heterogeneous platforms.
If I get it right, I need to have an ACPI HMAT table on the system
