diff options
| author | Connor Doyle <connor.p.d@gmail.com> | 2017-07-24 11:44:08 -0700 |
|---|---|---|
| committer | Connor Doyle <connor.p.d@gmail.com> | 2017-07-24 11:44:08 -0700 |
| commit | 3dfe261ede6c51543bfe5567c6d254186b3b2cd3 (patch) | |
| tree | 10c79dffd9ba47a753b4b8ea4a41a3144ce32ca7 | |
| parent | 8c9863645ce5e5efbfc52e9dd22dd520484ba28f (diff) | |
s/floor/ceiling, recommend integer allocatable.cpu
| -rw-r--r-- | contributors/design-proposals/cpu-manager.md | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/contributors/design-proposals/cpu-manager.md b/contributors/design-proposals/cpu-manager.md index 036e7547..e56074d8 100644 --- a/contributors/design-proposals/cpu-manager.md +++ b/contributors/design-proposals/cpu-manager.md @@ -146,9 +146,10 @@ configuration value `--cpu-manager-policy`. The default value is `noop`. The number of CPUs that pods may run on is set using the existing node-allocatable configuration settings. See the [node allocatable proposal document][node-allocatable] for details. The CPU manager will claim -`floor(node.status.allocatable.cpu)` as the number of CPUs available to assign -to pods, starting from the highest-numbered physical core and descending -topologically. +`ceiling(node.status.allocatable.cpu)` as the number of CPUs available to +assign to pods, starting from the highest-numbered physical core and +descending topologically. It is recommended to configure an integer value for +`node.status.allocatable.cpus` when the CPU manager is enabled. Operator documentation will be updated to explain how to configure the system to use the low-numbered physical cores for kube-reserved and |