Skip to content

Commit f3a655d

Browse files
Jeffwanklueska
andauthored
Update keps/sig-node/4176-cpumanager-spread-cpus-preferred-policy/README.md
Co-authored-by: Kevin Klues <[email protected]>
1 parent 077567c commit f3a655d

File tree

1 file changed

+1
-1
lines changed
  • keps/sig-node/4176-cpumanager-spread-cpus-preferred-policy

1 file changed

+1
-1
lines changed

keps/sig-node/4176-cpumanager-spread-cpus-preferred-policy/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -175,7 +175,7 @@ updates.
175175
[documentation style guide]: https://github.com/kubernetes/community/blob/master/contributors/guide/style-guide.md
176176
-->
177177

178-
We propose this KEP to introduce a new CPU Manager Static Policy Option that spreads hyper threads across physical cores. In this policy, we changed the cpu assignment sorting algorithm to sort by socket and then directly cpus without taking physical cores into ordering. It seems like a noisy neighbour issue, but it's always true. We will explain the reason in the motivation section. This policy is useful for some applications which need to take advantage of CPU Cache.
178+
In this KEP, we propose a new CPU Manager Static Policy Option called `distribute-cores-across-cpus` to prefer allocating cores from different physical CPUs on the same socket. This new policy is analogous to the `distribute-cpus-across-numa` policy option in that it proposes to *spread* cores allocations out, rather than pack them together. The main difference being that this new policy spreads individual core allocations across CPUs, whereas the existing policy spreads them across NUMA nodes. Such a policy is useful, for example, if an application wants to avoid being a noisy neighbor with itself, but still take advantage of the L2 cache by running its application threads on the same socket.
179179

180180
## Motivation
181181

0 commit comments

Comments
 (0)