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

feature request: socket topology #1599

Open
vsoch opened this issue Feb 24, 2024 · 9 comments
Open

feature request: socket topology #1599

vsoch opened this issue Feb 24, 2024 · 9 comments

Comments

@vsoch
Copy link

vsoch commented Feb 24, 2024

hiya! I'm looking to get a mapping of which cores belong to which socket, akin to what hwloc does: https://www.open-mpi.org/projects/hwloc/doc/v0.9.3/

Right now it looks like nfd exposes a cpu -> topology.socket_count which is great, but doesn't tell us about the topology. Would this be possible? Thanks!

@vsoch
Copy link
Author

vsoch commented Feb 24, 2024

I'm also not seeing basics about number of physical vs logical cores - that seems obvious like it should be here?

@marquiz
Copy link
Contributor

marquiz commented Feb 26, 2024

The node labels are not suitable for describing detailed hardware topology. I also think that the NodeFeature CRD isn't a very good at that. There's a separate nfd-topology-updater daemon that would be a better target for this feature – it exposes the topology via a separate CRD called NodeResourceTopology. The topology-updater currently exposes NUMA nodes only, not other aspects of the HW topology.

What is your use case for this request? How are you planning to consume the information?

@vsoch
Copy link
Author

vsoch commented Feb 26, 2024

I’m working on the compatibility specification for OCI and building extractor plugins and tools, for Kubernetes but also HPC. For a lot of HPC applications we want to know the detailed topology to best schedule work. https://www-hpc.cea.fr/tgcc-public/en/html/toc/fulldoc/Process_distribution_affinity_binding.html

@vsoch
Copy link
Author

vsoch commented Feb 26, 2024

It could be that hwloc is a better fit for this - I found a library in go but it has a bug so I opened an issue.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 26, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 25, 2024
@TessaIO
Copy link
Member

TessaIO commented Jun 25, 2024

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jun 25, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 23, 2024
@TessaIO
Copy link
Member

TessaIO commented Sep 23, 2024

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 23, 2024
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

5 participants