cgroups

From Wikipedia, the free encyclopedia
Jump to: navigation, search
cgroups
Original author(s) Paul Menage, Rohit Seth
Developer(s) Tejun Heo et al.
Initial release 2007; 7 years ago (2007)
Written in C
Operating system Linux
Type resource management for process groups
License GNU General Public License
Website www.kernel.org documentation
Linux kernel subsystems, cgroups are intertwined with many of them.

cgroups (control groups) is a Linux kernel feature to limit, account, and isolate resource usage (CPU, memory, disk I/O, etc.) of process groups.

This work was started by engineers at Google (primarily Paul Menage and Rohit Seth) in 2006 under the name "process containers";[1] in late 2007 it was renamed 'Control Groups' (due to the confusion caused by multiple meanings of the term "container" in the Linux kernel) and merged into kernel version 2.6.24.[2] Since then, many new features and controllers have been added, such as support for kernfs[3] and the introduction of a unified hierarchy.[4]

Features[edit]

One of the design goals of cgroups is to provide a unified interface to many different use cases, from controlling single processes (like nice) to whole operating system-level virtualization (like OpenVZ, Linux-VServer, LXC). Cgroups provides:

  • Resource limiting: groups can be set to not exceed a set memory limit — this also includes file system cache.[5] The original paper was presented at Linux Symposium and can be found at Containers: Challenges with the memory resource controller and its performance.[6]
  • Prioritization: some groups may get a larger share of CPU[7] or disk I/O throughput.[8]
  • Accounting: to measure how much resources certain systems use for e.g. billing purposes.[9]
  • Control: freezing groups or checkpointing and restarting.[9]

Usage[edit]

A control group is a collection of processes that are bound by the same criteria. These groups can be hierarchical, where each group inherits limits from its parent group. The kernel provides access to multiple controllers (subsystems) through the cgroup interface.[2] For instance, the "memory" controller limits memory use, "cpuacct" accounts CPU usage, etc.

Control groups can be used in multiple ways:

  • By accessing the cgroup virtual file system manually.
  • Create and manage groups on the fly using tools like cgcreate, cgexec, cgclassify (from libcgroup).
  • The "rules engine daemon" that can automatically move processes of certain users, groups, or commands to cgroups as specified in configuration.
  • Indirectly through other software that uses cgroups, such as Linux Containers (LXC) virtualization,[10] libvirt, systemd, Open Grid Scheduler/Grid Engine,[11] and Google's lmctfy.

The Linux kernel documentation contains full technical details of the setup and use of control groups.[12]

Namespace isolation[edit]

While not technically part of the cgroups work, a related feature of the Linux kernel is namespace isolation, where groups of processes are separated such that they cannot "see" resources in other groups. For example, a PID namespace provides a separate enumeration of process identifiers within each namespace. Also available are mount, UTS, network and SysV IPC namespaces.

  • The PID namespace provides isolation for the allocation of process identifiers (PIDs), lists of processes and their details. While the new namespace is isolated from other siblings, processes in its "parent" namespace still see all processes in child namespaces—albeit with different PID numbers.[13]
  • Network namespace isolates the network interface controllers (physical or virtual), iptables firewall rules, routing tables etc. Network namespaces can be connected with each other using the "veth" virtual Ethernet device.[14]
  • "UTS" namespace allows changing the hostname.
  • Mount namespace allows creating a different file system layout, or making certain mount points read-only.[15]
  • IPC namespace isolates the System V inter-process communication between namespaces.

Namespaces are created with the "unshare" command or syscall, or as new flags in a "clone" syscall.[16]

Early in cgroups development, the "ns" subsystem was added, to integrate namespaces and control groups. If the "ns" cgroup was mounted, each namespace would also create a new group in the cgroup hierarchy. This was an experiment that was later judged to be a poor fit for the cgroups API, and removed from the kernel.

Unified hierarchy[edit]

The Linux kernel facilities offered by the new "unified hierarchy" cgroups will only be accessible by and through systemd. The scheme hints, that cgroups are intertwined with many of the Linux kernel subsystems.

Whenever designing a software, the software engineer picks those solutions, which overall best blend the exigencies regarding stability, security, performance, as well as maintainability, programmability (API) and usability (ABI). By their nature, they balance each other, e.g. a mighty API to user space, that offers not too much functionality, but simply exposes some of the wrong inner workings, might seriously compromise kernel stability and security. That is especially true, if that software is part of the Linux kernel. Tejun Heo, decided to alter cgroups to that effect, that there will be one unified hierarchy and, that only one user space entity will have exclusive access to the facilities offered by cgroups.

Kernfs was introduced into the Linux kernel with version 3.14, the main author being Tejun Heo.[17] One of the main motivators for a separate kernfs is the cgroups file-system. Kernfs is basically the splitting off of some of the sysfs logic into an independent entity so that other kernel subsystems can more easily implement their own virtual file-system with handling for device connect and disconnect, dynamic creation and removal as needed or unneeded, and other attributes.

It is anticipated that debugfs will move to being Kernfs-based in the future as well.

Adoption[edit]

Various projects are using cgroups as their basis, including the following:

See also[edit]

References[edit]

  1. ^ Jonathan Corbet (29 May 2007). "Process containers". LWN.net. 
  2. ^ a b Jonathan Corbet (29 October 2007). "Notes from a container". LWN.net. 
  3. ^ "cgroup: convert to kernfs". 2014-01-28. 
  4. ^ "cgroup: prepare for the default unified hierarchy". 2014-03-13. 
  5. ^ Jonathan Corbet (31 July 2007). "Controlling memory use in containers". LWN. 
  6. ^ Balbir Singh, Vaidynathan Srinivasan (July 2007). "Containers: Challenges with the memory resource controller and its performance". Ottawa Linux Symposium. 
  7. ^ Jonathan Corbet (23 October 2007). "Kernel space: Fair user scheduling for Linux". Network World. Retrieved 2012-08-22. 
  8. ^ Kamkamezawa Hiroyu (19 November 2008). "Cgroup and Memory Resource Controller" (PDF presentation slides). Japan Linux Symposium. 
  9. ^ a b Dave Hansen. "Resource Management" (PDF presentation slides). Linux Foundation. 
  10. ^ Matt Helsley (3 February 2009). "LXC: Linux container tools". IBM developerWorks. 
  11. ^ "Grid Engine cgroups Integration". Scalable Logic. 2012-05-22. 
  12. ^ cgroups, kernel.org 
  13. ^ Pavel Emelyanov, Kir Kolyshkin (19 November 2007). "PID namespaces in the 2.6.24 kernel". LWN.net. 
  14. ^ Jonathan Corbet (30 January 2007). "Network namespaces". LWN.net. 
  15. ^ Serge E. Hallyn, Ram Pai (17 September 2007). "Applying mount namespaces". IBM developerWorks. 
  16. ^ Janak Desai (11 January 2006). "Linux kernel documentation on unshare". 
  17. ^ "kernfs, sysfs, driver-core: implement synchronous self-removal". LWN.net. 2014-02-03. Retrieved 2014-04-07. 

External links[edit]