You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Core scheduling support allows userspace to define groups of tasks that can share a core. These groups can be specified either for security usecases (one group of tasks don’t trust another), or for performance usecases (some workloads may benefit from running on the same core as they don’t need the same hardware resources of the shared core, or may prefer different cores if they do share hardware resource needs). This is achieved by setting and copying core scheduling task cookies between the threads (PID), processes (TGID), and process groups (PGID). See the kernel doc for further details.
This would be useful for all containers within a pod. Also, it is particularly helpful for multi-tenant environments.
Linux kernel 5.14 adds the support for Core Scheduling.
This allows setting and copying core scheduling 'task cookies' between
the container process and the threads (PID), processes (TGID), and
process groups (PGID), which helps define groups of tasks that can be
co-scheduled on the same core. These groups can be specified either for
security usecases or for performance usecases.
opencontainers#1113
Signed-off-by: Kailun Qin <kailun.qin@intel.com>
Linux 5.14 adds the support for Core Scheduling.
Core scheduling support allows userspace to define groups of tasks that can share a core. These groups can be specified either for security usecases (one group of tasks don’t trust another), or for performance usecases (some workloads may benefit from running on the same core as they don’t need the same hardware resources of the shared core, or may prefer different cores if they do share hardware resource needs). This is achieved by setting and copying core scheduling
task cookies
between the threads (PID), processes (TGID), and process groups (PGID). See the kernel doc for further details.This would be useful for all containers within a pod. Also, it is particularly helpful for multi-tenant environments.
runc requirement: opencontainers/runc#3061.
The text was updated successfully, but these errors were encountered: