From: Hui Su <sh_def@163.com>
To: tj@kernel.org, lizefan@huawei.com, hannes@cmpxchg.org,
corbet@lwn.net, cgroups@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: sh_def@163.com
Subject: [PATCH] Docs/cgroup: update the cgroup-v1 docs
Date: Mon, 2 Nov 2020 23:21:16 +0800 [thread overview]
Message-ID: <20201102152116.GA186491@rlk> (raw)
Since 'commit 69d0206c793a ("cgroup: bring some sanity to
naming around cg_cgroup_link")', 'cg_cgroup_link' has been
changed to 'cgrp_cset_link'.
so as its element 'cgrp_link_list' and 'cg_link_list'.
Since commit 47cfcd092245 ("cgroup: kill cgroup_[un]lock()"),
cgroup_lock/cgroup_unlock have been killed.
So update the cgroup-v1 Docs.
Signed-off-by: Hui Su <sh_def@163.com>
---
Documentation/admin-guide/cgroup-v1/cgroups.rst | 13 +++++--------
1 file changed, 5 insertions(+), 8 deletions(-)
diff --git a/Documentation/admin-guide/cgroup-v1/cgroups.rst b/Documentation/admin-guide/cgroup-v1/cgroups.rst
index b0688011ed06..c28316a7dd28 100644
--- a/Documentation/admin-guide/cgroup-v1/cgroups.rst
+++ b/Documentation/admin-guide/cgroup-v1/cgroups.rst
@@ -270,10 +270,10 @@ css_set is allocated. The appropriate existing css_set is located by
looking into a hash table.
To allow access from a cgroup to the css_sets (and hence tasks)
-that comprise it, a set of cg_cgroup_link objects form a lattice;
-each cg_cgroup_link is linked into a list of cg_cgroup_links for
-a single cgroup on its cgrp_link_list field, and a list of
-cg_cgroup_links for a single css_set on its cg_link_list.
+that comprise it, a set of cgrp_cset_link objects form a lattice;
+each cgrp_cset_link is linked into a list of cgrp_cset_links for
+a single cgroup on its cset_link field, and a list of
+cgrp_cset_links for a single css_set on its cgrp_link.
Thus the set of tasks in a cgroup can be listed by iterating over
each css_set that references the cgroup, and sub-iterating over
@@ -523,10 +523,7 @@ cgroup. It may also be taken to prevent cgroups from being
modified, but more specific locks may be more appropriate in that
situation.
-See kernel/cgroup.c for more details.
-
-Subsystems can take/release the cgroup_mutex via the functions
-cgroup_lock()/cgroup_unlock().
+See kernel/cgroup/cgroup.c for more details.
Accessing a task's cgroup pointer may be done in the following ways:
- while holding cgroup_mutex
--
2.29.0
next reply other threads:[~2020-11-02 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 15:21 Hui Su [this message]
2020-11-25 12:58 ` [PATCH] Docs/cgroup: update the cgroup-v1 docs Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201102152116.GA186491@rlk \
--to=sh_def@163.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).