[Local GC] GCToOSInterface TODO: CPUGroupInfo and NumaNodeInfo

[swgillespie]

  "CPUGroupInfo::CanEnableGCCPUGroups()", referenced from:
      SVR::gc_heap::create_gc_thread() in gcsvr.cpp.o
      SVR::GCHeap::Initialize() in gcsvr.cpp.o
  "CPUGroupInfo::GetGroupForProcessor(unsigned short, unsigned short*, unsigned short*)", referenced from:
      SVR::set_thread_group_affinity_for_heap(int, GCThreadAffinity*) in gcsvr.cpp.o
  "CPUGroupInfo::GetNumActiveProcessors()", referenced from:
      SVR::GCHeap::Initialize() in gcsvr.cpp.o
  "NumaNodeInfo::CanEnableGCNumaAware()", referenced from:
      SVR::set_thread_group_affinity_for_heap(int, GCThreadAffinity*) in gcsvr.cpp.o
      SVR::set_thread_affinity_mask_for_heap(int, GCThreadAffinity*) in gcsvr.cpp.o
      SVR::heap_select::init(int) in gcsvr.cpp.o
  "NumaNodeInfo::GetNumaProcessorNodeEx(_PROCESSOR_NUMBER*, unsigned short*)", referenced from:
      SVR::set_thread_group_affinity_for_heap(int, GCThreadAffinity*) in gcsvr.cpp.o
      SVR::set_thread_affinity_mask_for_heap(int, GCThreadAffinity*) in gcsvr.cpp.o

These will likely need to go into GCToOSInterface. Related to dotnet/coreclr#10938.

[janvorli]

@swgillespie this is where the experimental refactoring that I've made and shown you before could be used.
Here is the commit again for your reference: janvorli/coreclr@19bad47

[swgillespie]

@janvorli Great! Thank you!

[swgillespie]

Triage:

This issue does not require changes to the GC/EE interface but is desirable for performance on very high-scale machines. @janvorli 's changeset is still an excellent starting point.

Ultimately, as Jan's changeset indicates, NUMA and CPU group awareness should be implemented in GCToOSInterface.

[swgillespie]

Moving out to Future, this doesn't require any breaking changes to the GC/EE interface.

[ghost]

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

[ghost]

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.