From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.6 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B0A25C00A89 for ; Mon, 2 Nov 2020 15:38:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6653322258 for ; Mon, 2 Nov 2020 15:38:22 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=163.com header.i=@163.com header.b="HpXpF1Iu" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726385AbgKBPiW (ORCPT ); Mon, 2 Nov 2020 10:38:22 -0500 Received: from m12-12.163.com ([220.181.12.12]:49015 "EHLO m12-12.163.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726014AbgKBPiW (ORCPT ); Mon, 2 Nov 2020 10:38:22 -0500 X-Greylist: delayed 946 seconds by postgrey-1.27 at vger.kernel.org; Mon, 02 Nov 2020 10:38:20 EST DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Date:From:Subject:Message-ID:MIME-Version; bh=bxxfv 9QsqkbmxwfyzAF36u41WO4BWk6RMHqGjFs9RGQ=; b=HpXpF1IuLg/Mi8dh/7JI7 7aGzPE2LKjcW4yJgWKsL99ALbK0+q0SC14WqttzUxN+SV1RpxbYbWfzrAEXKhcNT tPylUlog14dyU8munfrzMxs3d9qYR6CuNVTbe7kEOTufkNDZohoDxvbscB/3m/QZ lJIZNb5+sxE53BeirmBtn8= Received: from localhost (unknown [101.228.30.230]) by smtp8 (Coremail) with SMTP id DMCowAAn82jsI6BfwibeUg--.53019S2; Mon, 02 Nov 2020 23:21:17 +0800 (CST) Date: Mon, 2 Nov 2020 23:21:16 +0800 From: Hui Su 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 Message-ID: <20201102152116.GA186491@rlk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-CM-TRANSID: DMCowAAn82jsI6BfwibeUg--.53019S2 X-Coremail-Antispam: 1Uf129KBjvJXoW7AryfCr43CF1DJFy3CFy5CFg_yoW8uF1xpr 1DA347X345Wwn0qryvy342ga4S9aykua17KFyrGrnYyrnxJr4vqFy2vr1UAFyvkF9xAFZx Xry3ur43ua1jy37anT9S1TB71UUUUU7qnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDUYxBIdaVFxhVjvjDU0xZFpf9x0zRDPEhUUUUU= X-Originating-IP: [101.228.30.230] X-CM-SenderInfo: xvkbvvri6rljoofrz/1tbiMQLQX1UMWNE16AAAsx Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org 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 --- 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