Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp201423rwb; Mon, 28 Nov 2022 19:18:53 -0800 (PST) X-Google-Smtp-Source: AA0mqf5HxKDYBURa1CqRyOR4n5gA0bC0maIb24BC8KPF8eptdoCjSvo2igQAODebSmuJj53ygyF4 X-Received: by 2002:a17:90a:4745:b0:213:1442:24be with SMTP id y5-20020a17090a474500b00213144224bemr62156098pjg.15.1669691933004; Mon, 28 Nov 2022 19:18:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669691932; cv=none; d=google.com; s=arc-20160816; b=YVfd0Lghc3t9xZpgIxXGu5zqftLsGDe0PB6hu7ippk5BVeGW8yvgb8yt9xaDQgPE15 YysROTKfRt4AtygdlcB9rNHOuMw8OcYvpJ4j73SeALQWdty9rXFdVMAUdnxEWinEoF6c jX+G3LeP5qh9jC88M4KokG5gGy2vMLNSgCCjzx55y9YkKEuduyP1QVMXkiVsn4Lui6hE qjGHwRnpFi7TDLB/t0qXeBPaWgRDZB9EOx0iL6uk0wafNHKVDQeAhrY4g6iPYxhyd5Na 0yeeKf//khsClCszcdH9OEmwRVMbf2CtHsYxAlI7wLzZz4YVG2Y2lrTLAzc75eUIPUc9 Kc1Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:in-reply-to:message-id :date:subject:cc:to:from; bh=gaxYLStHWF6T4kbi1isL/UNVCnxhiTfLl0Fiiab+aII=; b=0Fl4FKvl2Mw8jXbcTChNbi3BOosY6DN6cFJKXhFuJRTwyalb+hHkRSEqGBLH2s8J+L ViHxYlaTg9uSpDZPHuBOUzdSXvNEShl4lLBHLO6RCD2RomaKkvT+3khcICzOJB4WsIJ+ KsM7/Pl7Qa1QvWh4M/PDY6ElKohK2YYsNNSnEirD76w1Z/Y3isxuExkHmBw1C8oo+wZG r+JXcpCN1BmDPg5QatQLOonPjzj9tqXj3KuQ+76JGk6Fr7ZKj1UMvyfBD15ATB7rjKwG bNu9TJzRaF1bxidRFK0iDtEAbgBIXDbLTFz0luDJr6qoPEcCErSR90CPntuZrnQKU43m 9A5g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id 21-20020a170902c25500b001898ee9f701si3444184plg.2.2022.11.28.19.18.42; Mon, 28 Nov 2022 19:18:52 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235320AbiK2DCI (ORCPT + 83 others); Mon, 28 Nov 2022 22:02:08 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55922 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235205AbiK2DBx (ORCPT ); Mon, 28 Nov 2022 22:01:53 -0500 Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CA80C3D92C; Mon, 28 Nov 2022 19:01:52 -0800 (PST) Received: from kwepemi500016.china.huawei.com (unknown [172.30.72.54]) by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4NLnCn4JGkzCqj2; Tue, 29 Nov 2022 11:01:09 +0800 (CST) Received: from huawei.com (10.174.178.129) by kwepemi500016.china.huawei.com (7.221.188.220) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Tue, 29 Nov 2022 11:01:50 +0800 From: Kemeng Shi To: , , CC: , , , Subject: [PATCH v2 01/10] blk-throttle: correct stale comment in throtl_pd_init Date: Tue, 29 Nov 2022 11:01:38 +0800 Message-ID: <20221129030147.27400-2-shikemeng@huawei.com> X-Mailer: git-send-email 2.14.1.windows.1 In-Reply-To: <20221129030147.27400-1-shikemeng@huawei.com> References: <20221129030147.27400-1-shikemeng@huawei.com> MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.174.178.129] X-ClientProxiedBy: dggems702-chm.china.huawei.com (10.3.19.179) To kwepemi500016.china.huawei.com (7.221.188.220) X-CFilter-Loop: Reflected X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On the default hierarchy (cgroup2), the throttle interface files don't exist in the root cgroup, so the ablity to limit the whole system by configuring root group is not existing anymore. In general, cgroup doesn't wanna be in the business of restricting resources at the system level, so correct the stale comment that we can limit whole system to we can only limit subtree. Signed-off-by: Kemeng Shi --- block/blk-throttle.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/block/blk-throttle.c b/block/blk-throttle.c index 847721dc2b2b..59acfac87764 100644 --- a/block/blk-throttle.c +++ b/block/blk-throttle.c @@ -395,8 +395,9 @@ static void throtl_pd_init(struct blkg_policy_data *pd) * If on the default hierarchy, we switch to properly hierarchical * behavior where limits on a given throtl_grp are applied to the * whole subtree rather than just the group itself. e.g. If 16M - * read_bps limit is set on the root group, the whole system can't - * exceed 16M for the device. + * read_bps limit is set on a "parent" group, summary bps of + * "parent" group and its subtree groups can't exceed 16M for the + * device. * * If not on the default hierarchy, the broken flat hierarchy * behavior is retained where all throtl_grps are treated as if -- 2.30.0