Split L3 Cache Topology Awareness in CPU Manager

[sphrasavath]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  We proposed this KEP to introduce a new CPU Manager static policy option that makes best effort to align CPU resources by L3 (last-level) cache.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/4800-cpumanager-split-uncorecache/README.md (original in https://docs.google.com/document/d/1LpnMjGNsQyHOuVHMktIrjZsdRw9aKZ8djt354nAno6M/edit?usp=sharing) Previous issue Enhance CPU manager with L3 cache aware #2621
• Discussion Link:
• Primary contact (assignee): @sphrasavath, @wongchar, @ajcaldelas
• Responsible SIGs: Node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.32
  • Beta release target (x.y): 1.33
  • Stable release target (x.y): 1.35
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-4800: Split UnCoreCache awareness #4810
  • Code (k/k) update PR(s): Split L3 Cache Topology Awareness in CPU Manager kubernetes#126750
  • Docs (k/website) update PR(s): Add prefer-align-cpus-by-uncorecache feature gate website#48340

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[kannon92]

Are you all going to update the KEP? That link is old so I'm not sure your design still applies?

[kannon92]

/sig node

[kannon92]

First thing, please create a KEP PR where you fill in the template.

https://docs.google.com/document/d/1LpnMjGNsQyHOuVHMktIrjZsdRw9aKZ8djt354nAno6M/edit?usp=sharing

Does not suffice as a design doc.

[ffromani]

First thing, please create a KEP PR where you fill in the template.

https://docs.google.com/document/d/1LpnMjGNsQyHOuVHMktIrjZsdRw9aKZ8djt354nAno6M/edit?usp=sharing

Does not suffice as a design doc.

@sphrasavath Please make sure to use the very latest KEP template (just use the tip of the main branch), the template changes over time.
I agree there are more details to be filled, most of them the KEP template will make explicit.

[haircommander]

/assign @sphrasavath @wongchar @ajcaldelas

[k8s-ci-robot]

@haircommander: GitHub didn't allow me to assign the following users: wongchar, ajcaldelas.

Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @sphrasavath @wongchar @ajcaldelas

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.