-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Enhancement Split L3 Cache Topology Awareness in CPU Manager #4800
Comments
Are you all going to update the KEP? That link is old so I'm not sure your design still applies? |
/sig node |
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. |
/assign @sphrasavath @wongchar @ajcaldelas |
@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. In response to this:
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. |
/milestone v1.32 |
Hello @haircommander @sphrasavath 👋, v1.32 Enhancements team here. Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024. This enhancement is targeting for stage alpha for v1.32 (correct me, if otherwise). Here's where this enhancement currently stands:
For this KEP, we would need to update the following:
The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you! If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you! |
Enhancement Description
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.
k/enhancements
) update PR(s): KEP-4800: Split UnCoreCache awareness #4810k/k
) update PR(s): Split L3 Cache Topology Awareness in CPU Manager #126750k/website
) update PR(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: