[zh] Resync memory-manager.md

Author: zhuzhenghao

content/zh-cn/docs/tasks/administer-cluster/memory-manager.md

@@ -2,6 +2,7 @@
 title: 使用 NUMA 感知的内存管理器
 content_type: task
 min-kubernetes-server-version: v1.21
+weight: 410
 ---
 
 <!--
@@ -13,6 +14,7 @@ reviewers:
 
 content_type: task
 min-kubernetes-server-version: v1.21
+weight: 410
 -->
 
 <!-- overview -->
@@ -37,9 +39,8 @@ Kubernetes 内存管理器（Memory Manager）为 `Guaranteed`
 或者会被某节点接受，或者被该节点拒绝。
 
 <!--
-Moreover, the Memory Manager ensures that the memory which a pod
-requests is allocated from
-a minimum number of NUMA nodes.
+Moreover, the Memory Manager ensures that the memory which a pod requests
+is allocated from a minimum number of NUMA nodes.
 
 The Memory Manager is only pertinent to Linux based hosts.
 -->
@@ -52,7 +53,7 @@ The Memory Manager is only pertinent to Linux based hosts.
 {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
 
 <!--
-To align memory resources with other requested resources in a Pod Spec:
+To align memory resources with other requested resources in a Pod spec:
 
 - the CPU Manager should be enabled and proper CPU Manager policy should be configured on a Node.
   See [control CPU Management Policies](/docs/tasks/administer-cluster/cpu-management-policies/);
@@ -123,7 +124,7 @@ The complete flow diagram concerning pod admission and deployment process is ill
 
 <!--
 During this process, the Memory Manager updates its internal counters stored in
-[Node Map and Memory Maps][2] to manage guaranteed memory allocation. 
+[Node Map and Memory Maps][2] to manage guaranteed memory allocation.
 
 The Memory Manager updates the Node Map during the startup and runtime as follows.
 -->
@@ -158,8 +159,8 @@ The administrator must provide `--reserved-memory` flag when `Static` policy is
 ### 运行时  {#runtime} 
 
 <!--
-Reference [Memory Manager KEP: Memory Maps at runtime (with examples)][6]
-illustrates how a successful pod deployment affects the Node Map, and it also relates to
+Reference [Memory Manager KEP: Memory Maps at runtime (with examples)][6] illustrates
+how a successful pod deployment affects the Node Map, and it also relates to
 how potential Out-of-Memory (OOM) situations are handled further by Kubernetes or operating system.
 -->
 参考文献 [Memory Manager KEP: Memory Maps at runtime (with examples)][6]
@@ -173,7 +174,7 @@ attempts to create a group that comprises several NUMA nodes and features extend
 The problem has been solved as elaborated in
 [Memory Manager KEP: How to enable the guaranteed memory allocation over many NUMA nodes?][3].
 Also, reference [Memory Manager KEP: Simulation - how the Memory Manager works? (by examples)][1]
-illustrates how the management of groups occurs. 
+illustrates how the management of groups occurs.
 -->
 在内存管理器运作的语境中，一个重要的话题是对 NUMA 分组的管理。
 每当 Pod 的内存请求超出单个 NUMA 节点容量时，内存管理器会尝试创建一个包含多个
@@ -199,7 +200,7 @@ node stability (section [Reserved memory flag](#reserved-memory-flag)).
 （[预留内存标志](#reserved-memory-flag)）。
 
 <!--
-### Policies 
+### Policies
 -->
 ### 策略    {#policies}
 
@@ -222,7 +223,7 @@ This is the default policy and does not affect the memory allocation in any way.
 It acts the same as if the Memory Manager is not present at all.
 
 The `None` policy returns default topology hint. This special hint denotes that Hint Provider
-(Memory Manger in this case) has no preference for NUMA affinity with any resource.
+(Memory Manager in this case) has no preference for NUMA affinity with any resource.
 -->
 #### None 策略    {#policy-none}
 
@@ -234,7 +235,7 @@ The `None` policy returns default topology hint. This special hint denotes that
 <!--
 #### Static policy {#policy-static}
 
-In the case of the `Guaranteed` pod, the `Static` Memory Manger policy returns topology hints
+In the case of the `Guaranteed` pod, the `Static` Memory Manager policy returns topology hints
 relating to the set of NUMA nodes where the memory can be guaranteed,
 and reserves the memory through updating the internal [NodeMap][2] object.
 
@@ -275,7 +276,7 @@ The foregoing flags include `--kube-reserved`, `--system-reserved` and `--evicti
 The sum of their values will account for the total amount of reserved memory.
 
 A new `--reserved-memory` flag was added to Memory Manager to allow for this total reserved memory
-to be split (by a node administrator) and accordingly reserved across many NUMA nodes. 
+to be split (by a node administrator) and accordingly reserved across many NUMA nodes.
 -->
 Kubernetes 调度器在优化 Pod 调度过程时，会考虑“可分配的”内存。
 前面提到的标志包括 `--kube-reserved`、`--system-reserved` 和 `--eviction-threshold`。
@@ -287,7 +288,7 @@ Kubernetes 调度器在优化 Pod 调度过程时，会考虑“可分配的”
 <!--
 The flag specifies a comma-separated list of memory reservations of different memory types per NUMA node.
 Memory reservations across multiple NUMA nodes can be specified using semicolon as separator.
-This parameter is only useful in the context of the Memory Manager feature. 
+This parameter is only useful in the context of the Memory Manager feature.
 The Memory Manager will not use this reserved memory for the allocation of container workloads.
 
 For example, if you have a NUMA node "NUMA0" with `10Gi` of memory available, and
@@ -336,7 +337,7 @@ Also, avoid the following configurations:
    （特定的 `<size>` 的大页面也必须存在）。
 
 <!--
-Syntax: 
+Syntax:
 -->
 语法：
 
@@ -346,7 +347,7 @@ Syntax:
 * `N` (integer) - NUMA node index, e.g. `0`
 * `memory-type` (string) - represents memory type:
   * `memory` - conventional memory
-  * `hugepages-2Mi` or `hugepages-1Gi` - hugepages 
+  * `hugepages-2Mi` or `hugepages-1Gi` - hugepages
 * `value` (string) - the quantity of reserved memory, e.g. `1Gi`
 -->
 * `N`（整数）- NUMA 节点索引，例如，`0`
@@ -378,11 +379,11 @@ or
 <!--
 When you specify values for `--reserved-memory` flag, you must comply with the setting that
 you prior provided via Node Allocatable Feature flags.
-That is, the following rule must be obeyed for each memory type: 
+That is, the following rule must be obeyed for each memory type:
 
-`sum(reserved-memory(i)) = kube-reserved + system-reserved + eviction-threshold`, 
+`sum(reserved-memory(i)) = kube-reserved + system-reserved + eviction-threshold`,
 
-where `i` is an index of a NUMA node. 
+where `i` is an index of a NUMA node.
 -->
 当你为 `--reserved-memory` 标志指定取值时，必须要遵从之前通过节点可分配特性标志所设置的值。
 换言之，对每种内存类型而言都要遵从下面的规则：
@@ -395,7 +396,7 @@ where `i` is an index of a NUMA node.
 If you do not follow the formula above, the Memory Manager will show an error on startup.
 
 In other words, the example above illustrates that for the conventional memory (`type=memory`),
-we reserve `3Gi` in total, i.e.: 
+we reserve `3Gi` in total, i.e.:
 -->
 如果你不遵守上面的公式，内存管理器会在启动时输出错误信息。
 
@@ -412,12 +413,12 @@ An example of kubelet command-line arguments relevant to the node Allocatable co
 * `--system-reserved=cpu=123m,memory=333Mi`
 * `--eviction-hard=memory.available<500Mi`
 
-{{< note >}} 
+{{< note >}}
 <!--
 The default hard eviction threshold is 100MiB, and **not** zero.
 Remember to increase the quantity of memory that you reserve by setting `--reserved-memory`
 by that hard eviction threshold. Otherwise, the kubelet will not start Memory Manager and
-display an error. 
+display an error.
 -->
 默认的硬性驱逐阈值是 100MiB，**不是**零。
 请记得在使用 `--reserved-memory` 设置要预留的内存量时，加上这个硬性驱逐阈值。
@@ -430,10 +431,10 @@ Here is an example of a correct configuration:
 下面是一个正确配置的示例：
 
 ```shell
---feature-gates=MemoryManager=true 
---kube-reserved=cpu=4,memory=4Gi 
---system-reserved=cpu=1,memory=1Gi 
---memory-manager-policy=Static 
+--feature-gates=MemoryManager=true
+--kube-reserved=cpu=4,memory=4Gi
+--system-reserved=cpu=1,memory=1Gi
+--memory-manager-policy=Static
 --reserved-memory '0:memory=3Gi;1:memory=2148Mi'
 ```
 
@@ -527,7 +528,7 @@ became rejected at a node:
 - pod status - indicates topology affinity errors
 - system logs - include valuable information for debugging, e.g., about generated hints
 - state file - the dump of internal state of the Memory Manager
-  (includes [Node Map and Memory Maps][2]) 
+  (includes [Node Map and Memory Maps][2])
 - starting from v1.22, the [device plugin resource API](#device-plugin-resource-api) can be used
   to retrieve information about the memory reserved for containers
 -->
@@ -543,7 +544,7 @@ became rejected at a node:
 This error typically occurs in the following situations:
 
 * a node has not enough resources available to satisfy the pod's request
-* the pod's request is rejected due to particular Topology Manager policy constraints 
+* the pod's request is rejected due to particular Topology Manager policy constraints
 
 The error appears in the status of a pod:
 -->
@@ -579,7 +580,7 @@ Warning  TopologyAffinityError  10m   kubelet, dell8  Resources cannot be alloca
 
 Search system logs with respect to a particular pod.
 
-The set of hints that Memory Manager generated for the pod can be found in the logs. 
+The set of hints that Memory Manager generated for the pod can be found in the logs.
 Also, the set of hints generated by CPU Manager should be present in the logs.
 -->
 ### 系统日志     {#system-logs}
@@ -595,7 +596,7 @@ The best hint should be also present in the logs.
 
 The best hint indicates where to allocate all the resources.
 Topology Manager tests this hint against its current policy, and based on the verdict,
-it either admits the pod to the node or rejects it.  
+it either admits the pod to the node or rejects it.
 
 Also, search the logs for occurrences associated with the Memory Manager,
 e.g. to find out information about `cgroups` and `cpuset.mems` updates.
@@ -636,7 +637,7 @@ spec:
         cpu: "2"
         memory: 150Gi
     command: ["sleep","infinity"]
-``` 
+```
 
 <!--
 Next, let us log into the node where it was deployed and examine the state file in
@@ -724,14 +725,14 @@ It can be deduced from the state file that the pod was pinned to both NUMA nodes
    0,
    1
 ],
-``` 
+```
 
 <!--
 Pinned term means that pod's memory consumption is constrained (through `cgroups` configuration)
 to these NUMA nodes.
 
 This automatically implies that Memory Manager instantiated a new group that
-comprises these two NUMA nodes, i.e. `0` and `1` indexed NUMA nodes. 
+comprises these two NUMA nodes, i.e. `0` and `1` indexed NUMA nodes.
 -->
 术语绑定（pinned）意味着 Pod 的内存使用被（通过 `cgroups` 配置）限制到这些 NUMA 节点。
 
@@ -743,7 +744,7 @@ Notice that the management of groups is handled in a relatively complex manner,
 further elaboration is provided in Memory Manager KEP in [this][1] and [this][3] sections.
 
 In order to analyse memory resources available in a group,the corresponding entries from
-NUMA nodes belonging to the group must be added up.  
+NUMA nodes belonging to the group must be added up.
 -->
 注意 NUMA 分组的管理是有一个相对复杂的管理器处理的，
 相关逻辑的进一步细节可在内存管理器的 KEP 中[示例1][1]和[跨 NUMA 节点][3]节找到。
@@ -791,7 +792,7 @@ kubelet 提供了一个 `PodResourceLister` gRPC 服务来启用对资源和相
 <!--
 以下均为英文设计文档，因此其标题不翻译。
 -->
-- [Memory Manager KEP: Design Overview][4] 
+- [Memory Manager KEP: Design Overview][4]
 - [Memory Manager KEP: Memory Maps at start-up (with examples)][5]
 - [Memory Manager KEP: Memory Maps at runtime (with examples)][6]
 - [Memory Manager KEP: Simulation - how the Memory Manager works? (by examples)][1]
@@ -804,4 +805,3 @@ kubelet 提供了一个 `PodResourceLister` gRPC 服务来启用对资源和相
 [4]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/1769-memory-manager#design-overview
 [5]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/1769-memory-manager#memory-maps-at-start-up-with-examples
 [6]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/1769-memory-manager#memory-maps-at-runtime-with-examples
-