Enhance CPU manager with L3 cache aware

[hustcat]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  Some CPUs, such as AMD Rome, each CPU package(socket) have multiple L3 caches. When allocating CPUs, L3 cache should be considered.

• Kubernetes Enhancement Proposal:

• Discussion Link:

• Primary contact (assignee): @hustcat @ranchothu

• Responsible SIGs: node

• Enhancement target (which target equals to which milestone):

  • Alpha release target (x.y): v1.22
  • Beta release target (x.y):
  • Stable release target (x.y):

• Alpha

  • KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s):
  • Docs (k/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.

[hustcat]

/sig node

[hustcat]

/assign @ranchothu @hustcat

[k8s-ci-robot]

@hustcat: GitHub didn't allow me to assign the following users: ranchothu.

Note that only kubernetes members, 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 @ranchothu @hustcat

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/test-infra repository.

[ffromani]

Hi! there is already a conversation (maybe a github issue?) in place on cadvisor project to report the informations about llc so kubelet can consume them? Could you please link it here maybe?

[ffromani]

Hi! there is already a conversation (maybe a github issue?) in place on cadvisor project to report the informations about llc so kubelet can consume them? Could you please link it here maybe?

nevermind, I just realized you documented in the KEP text itself.

[hustcat]

https://docs.google.com/document/d/1BuiBgsittUnU3heKHRCQ66YYxzAItT5gcPlu3N83PfA/edit?usp=sharing
This is the design document.

[k8s-triage-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[ffromani]

/remove-lifecycle stale