Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
documentation.suse.com › Documentación de SUSE Linux Enterprise Server › System Analysis and Tuning Guide › Resource Management › Kernel Control Groups
ContentsContents
System Analysis and Tuning Guide
  1. About This Guide
  2. I Basics
    1. 1 General Notes on System Tuning
  3. II System Monitoring
    1. 2 System Monitoring Utilities
    2. 3 Analyzing and Managing System Log Files
  4. III Kernel Monitoring
    1. 4 SystemTap—Filtering and Analyzing System Data
    2. 5 Kernel Probes
    3. 6 Hardware-Based Performance Monitoring with Perf
    4. 7 OProfile—System-Wide Profiler
  5. IV Resource Management
    1. 8 General System Resource Management
    2. 9 Kernel Control Groups
    3. 10 Automatic Non-Uniform Memory Access (NUMA) Balancing
    4. 11 Power Management
  6. V Kernel Tuning
    1. 12 Tuning I/O Performance
    2. 13 Tuning the Task Scheduler
    3. 14 Tuning the Memory Management Subsystem
    4. 15 Tuning the Network
  7. VI Handling System Dumps
    1. 16 Tracing Tools
    2. 17 Kexec and Kdump
    3. 18 Using systemd-coredump to Debug Application Crashes
  8. VII Synchronized Clocks with Precision Time Protocol
    1. 19 Precision Time Protocol
  9. A GNU Licenses
Navigation←→
documentation.suse.com › Documentación de SUSE Linux Enterprise Server › System Analysis and Tuning Guide › Resource Management › Kernel Control Groups
Top
←→
Applies to SUSE Linux Enterprise Server 12 SP5

9 Kernel Control Groups

Abstract

Kernel Control Groups (“cgroups”) are a kernel feature that allows assigning and limiting hardware and system resources for processes. Processes can also be organized in a hierarchical tree structure.

9.1 Overview
9.2 Setting Resource Limits
9.3 For More Information

9.1 Overview

Every process is assigned exactly one administrative cgroup. cgroups are ordered in a hierarchical tree structure. Resource limitations can be set for single processes or for whole branches of the hierarchy tree. Limitations for CPU, memory, disk I/O, or network bandwidth usage can be set.

On SUSE Linux Enterprise Server, systemd uses cgroups to organize all processes in groups, which systemd calls slices. systemd also provides an interface for setting cgroup properties.

The command systemd-cgls displays the hierarchy tree.

This chapter is an overview. For more details, refer to the listed references.

9.2 Setting Resource Limits

Note
Note: Implicit Resource Consumption

Be aware that resource consumption implicitly depends on the environment where your workload executes (e.g. size of data structures in libraries/kernel, forking behavior of utilities, computational efficiency), hence it is recommended to (re)calibrate your limits should the environment change.

Limitations for cgroups can be set with the systemctl set-property command. The syntax is: 

root # systemctl set-property [--runtime] NAME PROPERTY1=VALUE [PROPERTY2=VALUE]

Optionally, use the --runtime option. With this option, set limits do not persist after the next reboot.

Replace NAME with a systemd service slice, scope, socket, mount, or swap name. Replace properties with one or more of the following:

CPUAccounting=[yes|no]

Turns on CPU usage accounting. This property takes yes and no as arguments.

Example: 

root # systemctl set-property user.slice CPUAccounting=yes
CPUQuota=PERCENTAGE

Assigns a CPU time to processes. The value is a percentage followed by a % as suffix. This requires CPUAccounting=yes.

Example: 

root # systemctl set-property user.slice CPUQuota=50%
MemoryAccounting=[yes|no]

Turns on memory usage accounting. This property takes yes and no as arguments.

Example: 

root # systemctl set-property user.slice MemoryAccounting=yes
MemoryLow=BYTES

Unused memory from processes below this limit will not be reclaimed for other use. Use suffixes K, M, G or T for BYTES. This requires MemoryAccounting=yes.

Example: 

root # systemctl set-property nginx.service MemoryLow=512M
MemoryHigh=BYTES

If more memory above this limit is used, memory is aggressively taken away from the processes. Use suffixes K, M, G or T for BYTES. This requires MemoryAccounting=yes.

Example: 

root # systemctl set-property nginx.service MemoryHigh=2G
MemoryMax=BYTES

Sets a maximum limit for used memory. Processes will be killed if they use more memory than allowed. Use suffixes K, M, G or T for BYTES. This requires MemoryAccounting=yes.

Example: 

root # systemctl set-property nginx.service MemoryMax=4G
DeviceAllow=

Allows read (r), write (w) and mknod (m) access. The command takes a device node specifier and a list of r, w or m, separated by a white space.

Example: 

root # systemctl set-property system.slice DeviceAllow="/dev/sdb1 r"
DevicePolicy=[auto|closed|strict]

When set to strict, only access to devices that are listed in DeviceAllow is allowed. closed additionally allows access to standard pseudo devices including /dev/null, /dev/zero, /dev/full, /dev/random, and /dev/urandom. auto allows access to all devices if no specific rule is defined in DeviceAllow. auto is the default setting.

For more details and a complete list of properties, see man systemd.resource-control.

9.3 For More Information

→Chapter 10 Automatic Non-Uniform Memory Access (NUMA) Balancing←Chapter 8 General System Resource Management
Print this page

© 2022 SUSE