summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSeth Jennings <sjenning@redhat.com>2017-08-21 22:58:44 -0500
committerSeth Jennings <sjenning@redhat.com>2017-08-21 22:59:49 -0500
commitb9a227bf353207c1548f6b3f028deed394b68e39 (patch)
tree40620a3f452fff3f7e0894ee1d275120bf021b9d
parent97ac742613e1cc176d0d4d06193dcd6e50b7ff03 (diff)
fix typos in cpu-manager proposal
-rw-r--r--contributors/design-proposals/cpu-manager.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/contributors/design-proposals/cpu-manager.md b/contributors/design-proposals/cpu-manager.md
index f54c52c5..e8ea0ce0 100644
--- a/contributors/design-proposals/cpu-manager.md
+++ b/contributors/design-proposals/cpu-manager.md
@@ -35,7 +35,7 @@ _Solution requirements:_
sure that the pod gets its cpu quota primarily from reserved core(s),
resulting in fewer context switches and higher cache affinity".
1. Support the case where in a given pod, one container is latency-critical
- and another is not (e.g. auxillary side-car containers responsible for
+ and another is not (e.g. auxiliary side-car containers responsible for
log forwarding, metrics collection and the like.)
1. Do not cap CPU quota for guaranteed containers that are granted
exclusive cores, since that would be antithetical to (1) above.
@@ -110,18 +110,18 @@ type State interface {
GetCPUSet(containerID string) (cpuset.CPUSet, bool)
GetDefaultCPUSet() cpuset.CPUSet
GetCPUSetOrDefault(containerID string) cpuset.CPUSet
- GetPresure() bool
+ GetPressure() bool
SetCPUSet(containerID string, cpuset CPUSet)
SetDefaultCPUSet(cpuset CPUSet)
Delete(containerID string)
- SetPresure(value bool)
+ SetPressure(value bool)
}
type Manager interface {
Start()
RegisterContainer(p *Pod, c *Container, containerID string) error
UnregisterContainer(containerID string) error
- IsUnderCPUPresure() bool
+ IsUnderCPUPressure() bool
State() state.Reader
}