You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Linux 6.1, the kernel may demote/promote memory from/to fast/slow memory (if /sys/kernel/mm/numa/demotion_enabled is true). This uses tiers defined in /sys/devices/virtual/memory_tiering. On a machine with 4 DRAM nodes and 2 PMEM nodes, you'll see one tier with DRAM numa nodes and one with PMEM numa nodes:
This could help identify PMEM/DRAM/HBM nodes in hwloc, but it's not clear yet if the kernel uses some info that hwloc doesn't have. For now (6.5), it seems to just use a static "abstract distance" that is 576 for DRAM (tier4 is 576/128=4) and 2280 for DAX KMEM (tier22 is 2280/128=22) so far. DAX KMEM for HBM should have a different value but it doesn't seem to be the case yet.
Memory types are registered with init_node_memory_type(). In mm/memory-tiers.c, all nodes are set to DRAM using
__init_node_memory_type(node, default_dram_type);
In drivers/dax/kmem.c, NVM (likely HBM/SPM too) are set to slow tier:
Since Linux 6.1, the kernel may demote/promote memory from/to fast/slow memory (if /sys/kernel/mm/numa/demotion_enabled is true). This uses tiers defined in /sys/devices/virtual/memory_tiering. On a machine with 4 DRAM nodes and 2 PMEM nodes, you'll see one tier with DRAM numa nodes and one with PMEM numa nodes:
This could help identify PMEM/DRAM/HBM nodes in hwloc, but it's not clear yet if the kernel uses some info that hwloc doesn't have. For now (6.5), it seems to just use a static "abstract distance" that is 576 for DRAM (tier4 is 576/128=4) and 2280 for DAX KMEM (tier22 is 2280/128=22) so far. DAX KMEM for HBM should have a different value but it doesn't seem to be the case yet.
Memory types are registered with
init_node_memory_type()
. In mm/memory-tiers.c, all nodes are set to DRAM usingIn drivers/dax/kmem.c, NVM (likely HBM/SPM too) are set to slow tier:
The text was updated successfully, but these errors were encountered: