User Tools

Site Tools


linux:kernel:control_groups

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
linux:kernel:control_groups [2019/12/15 21:55] peterlinux:kernel:control_groups [2020/07/15 09:30] (current) – external edit 127.0.0.1
Line 115: Line 115:
   * **release_agent**: the path to use for release notifications (this file exists in the top cgroup only).   * **release_agent**: the path to use for release notifications (this file exists in the top cgroup only).
  
-Other subsystems such as [[Kernel:CPU Sets|cpusets]] may add additional files in each cgroup dir.+Other subsystems such as [[Linux:Kernel:CPU Sets|cpusets]] may add additional files in each cgroup dir.
  
 New cgroups are created using the mkdir system call or shell command.  The properties of a cgroup, such as its flags, are modified by writing to the appropriate file in that cgroups directory, as listed above. New cgroups are created using the mkdir system call or shell command.  The properties of a cgroup, such as its flags, are modified by writing to the appropriate file in that cgroups directory, as listed above.
Line 453: Line 453:
 </code> </code>
  
-Called at the end of **cgroup_clone()** to do any parameter initialization which might be required before a task could attach.  For example in [[Kernel:CPU Sets|cpusets]], no task may attach before 'cpus' and 'mems' are set up.+Called at the end of **cgroup_clone()** to do any parameter initialization which might be required before a task could attach.  For example in [[Linux:Kernel:CPU Sets|cpusets]], no task may attach before 'cpus' and 'mems' are set up.
  
 <code c> <code c>
linux/kernel/control_groups.1576446934.txt.gz · Last modified: 2020/07/15 09:30 (external edit)

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki