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
I'm actually not sure which Win32 subsystem or WMI table holds information about the socket and memory topology for the hardware, so we'll have to figure that out.
Because WMI is based on CIM, which is horrendously awful and created before most modern hardware, after much research, it seems I'll have to rely on the Win32 kernel GetLogicalProcessorInformation API call:
Activity
jaypipes commentedon Feb 15, 2020
Because WMI is based on CIM, which is horrendously awful and created before most modern hardware, after much research, it seems I'll have to rely on the Win32 kernel GetLogicalProcessorInformation API call:
https://docs.microsoft.com/en-us/windows/win32/api/sysinfoapi/nf-sysinfoapi-getlogicalprocessorinformation?redirectedfrom=MSDN
Which we'll probably need to use the
unsafeandgolang.org/x/sys/windows/registrypackages with.[windows] find processor topology info
[windows] find processor topology info
[windows] find processor topology info (#192)