cgroups.7: tfix

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2016-04-25 08:48:35 +02:00
parent f0d27655d0
commit 94eeedfd20
1 changed files with 6 additions and 6 deletions

View File

@ -84,7 +84,7 @@ The existing subsystems include:
.IP *
.I perf_event
.IP *
.I net_pri
.I net_prio
.IP *
.I hugetlb
.IP *
@ -106,7 +106,7 @@ Since they are exposed through a virtual filesystem, subsystems
must be mounted before they can be controlled.
The usual place for this is under
.I /sys/fs/cgroup.
If all the desired subsystems can be co-mounted,
If all the desired subsystems can be comounted,
then the system may simply
mount -t cgroup cgroup /sys/fs/cgroup
@ -133,8 +133,8 @@ done
.in
.fi
Co-mounting subsystems has the effect that a task is in the same cgroup for
all co-mounted subsystems.
Comounting subsystems has the effect that a task is in the same cgroup for
all comounted subsystems.
Separately mounting subsystems allows a task to
be in cgroup
.I /foo1
@ -241,7 +241,7 @@ the new semantics are hidden behind a mount option
mount -t cgroup -o __DEVEL__sane_behavior cgroup /sys/fs/cgroup
By default, all controllers are co-mounted in the unified hierarchy.
By default, all controllers are comounted in the unified hierarchy.
While controllers may be mounted under the legacy hierarchy,
they may not be mounted at the same time in legacy and unified hierarchies.
@ -291,7 +291,7 @@ file in the kernel source.
.SS Subsystems
.TP
.I cpu
Cgroups can be guaranteed a minimum number of "cpu shares"
Cgroups can be guaranteed a minimum number of "CPU shares"
when a system is busy.
This does not limit a cgroup's CPU usage if the CPUs are not busy.
.TP