Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose memory tiers to command-line tools #613

Closed
bgoglin opened this issue Aug 28, 2023 · 1 comment
Closed

Expose memory tiers to command-line tools #613

bgoglin opened this issue Aug 28, 2023 · 1 comment

Comments

@bgoglin
Copy link
Contributor

bgoglin commented Aug 28, 2023

hwloc-bind has --hbm and --no-hbm to filter HBMs in membind locations. This could be extended to hwloc-calc (both for input and output). And this should be extended to more than just HBM. We have some notion of memory tiers internally to detect what's DDR, HBM, NVM or SPM. Linux has some info too #576. We could use that in hwloc-bind and hwloc-calc , for instance for finding how the machine is divided by some sort of memory.

In the future, we could have an API to query memory tiers. But right now, a simple memory attribute in NUMA node, for instance MemoryTier=2 (value for the internal ranking of nodes based of performance) might be enough.

This internally memtier ranking envvar configuration could be extended, for instance if somebody wants to rank by latency instead of bandwidth. And it could even be overriden by an envvar such as HWLOC_MEMTIERS=HBM=0x0f;DDR=0xf;NVM=0x00f.

This will likely supersede the hwloc-calc part of #612.

@bgoglin
Copy link
Contributor Author

bgoglin commented Oct 27, 2023

This is fixed in master thanks to #630 and backported to 2.x

@bgoglin bgoglin closed this as completed Oct 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant