summaryrefslogtreecommitdiff
path: root/Documentation/admin-guide/cgroup-v1
diff options
context:
space:
mode:
authorBagas Sanjaya <bagasdotme@gmail.com>2023-01-05 20:16:28 +0700
committerTejun Heo <tj@kernel.org>2023-01-05 07:38:10 -1000
commiteb08489448fbc70eda1ba6cfdddd59de00ddf941 (patch)
treef1f9e7c8fc28698654f3446f229d94b09cdb88aa /Documentation/admin-guide/cgroup-v1
parent4ddb1a2aa1a3c4317b94417f1bace0e4f06f51b9 (diff)
docs: cgroup-v1: use code block for locking order schema
The locking order schema is a figure (like diagram), which should have been formatted with literal code block for consistency with other figures. Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com> Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'Documentation/admin-guide/cgroup-v1')
-rw-r--r--Documentation/admin-guide/cgroup-v1/memory.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/admin-guide/cgroup-v1/memory.rst b/Documentation/admin-guide/cgroup-v1/memory.rst
index b0353c40639b..2b807fc128c6 100644
--- a/Documentation/admin-guide/cgroup-v1/memory.rst
+++ b/Documentation/admin-guide/cgroup-v1/memory.rst
@@ -287,7 +287,7 @@ When oom event notifier is registered, event will be delivered.
2.6 Locking
-----------
-Lock order is as follows:
+Lock order is as follows::
Page lock (PG_locked bit of page->flags)
mm->page_table_lock or split pte_lock