summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVladimir Rutsky <rutsky@google.com>2018-01-02 17:27:41 +0100
committerTejun Heo <tj@kernel.org>2018-01-02 08:33:47 -0800
commit2877cbe6501e20dd076c7677f768d50bcc87267b (patch)
treebe5b19ce06117ca358b9ae0722eb12161d80174d
parent392536b731cfe82eea414f4b09c128ef37cd477e (diff)
cgroup-v2.txt: fix typos
Signed-off-by: Vladimir Rutsky <rutsky@google.com> Signed-off-by: Tejun Heo <tj@kernel.org>
-rw-r--r--Documentation/cgroup-v2.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/cgroup-v2.txt b/Documentation/cgroup-v2.txt
index d6efabb487e3..c783bbb9d0fb 100644
--- a/Documentation/cgroup-v2.txt
+++ b/Documentation/cgroup-v2.txt
@@ -280,7 +280,7 @@ thread mode, the following conditions must be met.
exempt from this requirement.
Topology-wise, a cgroup can be in an invalid state. Please consider
-the following toplogy::
+the following topology::
A (threaded domain) - B (threaded) - C (domain, just created)
@@ -1064,10 +1064,10 @@ PAGE_SIZE multiple when read back.
reached the limit and allocation was about to fail.
Depending on context result could be invocation of OOM
- killer and retrying allocation or failing alloction.
+ killer and retrying allocation or failing allocation.
Failed allocation in its turn could be returned into
- userspace as -ENOMEM or siletly ignored in cases like
+ userspace as -ENOMEM or silently ignored in cases like
disk readahead. For now OOM in memory cgroup kills
tasks iff shortage has happened inside page fault.
@@ -1192,7 +1192,7 @@ PAGE_SIZE multiple when read back.
cgroups. The default is "max".
Swap usage hard limit. If a cgroup's swap usage reaches this
- limit, anonymous meomry of the cgroup will not be swapped out.
+ limit, anonymous memory of the cgroup will not be swapped out.
Usage Guidelines