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.

Sign up for GitHub

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

Jump to bottom

add support for new Die, Module and NumaNodeEx relationship in Windows #465

Open
bgoglin opened this issue Apr 22, 2021 · 1 comment
Open

add support for new Die, Module and NumaNodeEx relationship in Windows #465

bgoglin opened this issue Apr 22, 2021 · 1 comment
Labels
enhancement Windows

Comments

@bgoglin
Copy link
Contributor

bgoglin commented Apr 22, 2021 •
edited

Die, Module and a new NumaNodeEx are coming to Windows processor relationship API.
Die is likely what's exposed by x86 CPUID 0x1f leaf on Xeon AP.
Module could be either x86 CPUID 0x1f too but it's not exposed by any hardware yet, and why not expose Tile too? Or it's something different.
NumaNodeEx is only used on input (for requesting NUMA affinity in new format that may span multiple processor groupes). All returns that as well.
bgoglin added a commit to bgoglin/hwloc that referenced this issue Nov 9, 2021
@bgoglin
windows: support multiple Groups per NUMA
189ea79 
The previous Windows API could not describe NUMA nodes with PUs
from more than a single Processor Group (64 PUs max).

Starting with Windows 10 build 20348 and Windows 11, the NUMA affinity
can be described in more than one group affinity structure.

Refs open-mpi#465

Signed-off-by: Brice Goglin <Brice.Goglin@inria.fr>
bgoglin added a commit to bgoglin/hwloc that referenced this issue Nov 9, 2021
@bgoglin
windows: support multiple processor Groups per NUMA
f28af21 
The previous Windows API could not describe NUMA nodes with PUs
from more than a single Processor Group (64 PUs max).

Starting with Windows 10 build 20348 and Windows 11, the NUMA affinity
can be described in more than one group affinity structure.

Refs open-mpi#465

Signed-off-by: Brice Goglin <Brice.Goglin@inria.fr>
bgoglin added a commit to bgoglin/hwloc that referenced this issue Nov 11, 2021
@bgoglin
windows: support multiple processor Groups per NUMA
17200fc 
The previous Windows API could not describe NUMA nodes with PUs
from more than a single Processor Group (64 PUs max).

Starting with Windows 10 build 20348 and Windows 11, the NUMA affinity
can be described in more than one group affinity structure.

Refs open-mpi#465

Signed-off-by: Brice Goglin <Brice.Goglin@inria.fr>
bgoglin added a commit to bgoglin/hwloc that referenced this issue Nov 11, 2021
@bgoglin
windows: support multiple processor Groups per cache
0fdd600 
The previous Windows API could not describe caches with PUs
from more than a single Processor Group (64 PUs max).
This was extended for NUMA nodes in Windows 10 build 20348
and Windows 11 (see previous commit), and approximately at
the same time for caches.

Refs open-mpi#465

Signed-off-by: Brice Goglin <Brice.Goglin@inria.fr>
bgoglin added a commit to bgoglin/hwloc that referenced this issue Nov 13, 2021
@bgoglin
windows: support multiple processor Groups per NUMA
0185d00 
The previous Windows API could not describe NUMA nodes with PUs
from more than a single Processor Group (64 PUs max).

Starting with Windows 10 build 20348 and Windows 11, the NUMA affinity
can be described in more than one group affinity structure.

Refs open-mpi#465

Signed-off-by: Brice Goglin <Brice.Goglin@inria.fr>
bgoglin added a commit to bgoglin/hwloc that referenced this issue Nov 13, 2021
@bgoglin
windows: support multiple processor Groups per cache
5858e76 
The previous Windows API could not describe caches with PUs
from more than a single Processor Group (64 PUs max).

This was extended for NUMA nodes in Windows 10 build 20348
and Windows 11 (see previous commit), and approximately at
the same time for caches.

Refs open-mpi#465

Signed-off-by: Brice Goglin <Brice.Goglin@inria.fr>
@bgoglin
Copy link
Contributor Author

bgoglin commented Oct 27, 2023

See #480

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Windows
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bgoglin