From adaa5170f48e5d969ef1a335a55c5c9ae882f030 Mon Sep 17 00:00:00 2001 From: Kir Kolyshkin Date: Tue, 16 Jul 2024 19:23:24 -0700 Subject: [PATCH] config: simplify final CPU affinity rule Description of execCPUAffinity.final said that if it's not set or empty, the final affinity is the one of container's cgroup. This was done because we thought the kernel changes process' CPU affinity to one of cgroup. It's not the case. To keep the runtime simple, it makes sense to not do anything if the final affinity is not explicitly set. This change does just that. Signed-off-by: Kir Kolyshkin --- config.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/config.md b/config.md index b9b55737c..824de93d0 100644 --- a/config.md +++ b/config.md @@ -349,8 +349,9 @@ For Linux-based systems, the `process` object supports the following process-spe ranges. For example, `0-3,7` represents CPUs 0,1,2,3, and 7. * **`final`** (string, OPTIONAL) is a list of CPUs the process will be run on after the transition to container's cgroup. The format is the same as - for `initial`. If omitted or empty, the container's default CPU affinity, - as defined by [cpu.cpus property](./config.md#configLinuxCPUs)), is used. + for `initial`. If omitted or empty, runtime SHOULD NOT change process' + CPU affinity after the process is moved to container's cgroup, and the + final affinity is determined by the Linux kernel. ### User