Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp228239rwd; Tue, 6 Jun 2023 22:04:38 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4XiHoJK8mTSbD6sv6879WaachtUvdM34wZInY+zo4D8RUO54cnele2QItueS1Pb08IShRf X-Received: by 2002:a17:902:d487:b0:1af:d812:d27 with SMTP id c7-20020a170902d48700b001afd8120d27mr5251545plg.9.1686114277841; Tue, 06 Jun 2023 22:04:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1686114277; cv=none; d=google.com; s=arc-20160816; b=R71VzAUc5rKI1E5d0LYC1ksgOxXXPl1+B5pH9E8cAOSrZY5X4khS/ECMebl3GerZ4i EvUW55OEykYmkTJ2ElZ5yVRS2Z5sLKV4rkoik+weGa/ccPFqsF+ObLwLcsI1p5L+KnPa EklpUoioa1ljqxeznfKfLaLjlZu/dAAzxWWN+V7GkUi+AuMWsbLMZtgo23zm9zBJb/ip 871fGvkKkMFjl0fkLlsTe0/CfUX4/V0gCI5bPw5Gr4FsSRRZTp5CekndzNZGeldag4mj E/5eksSydPCS/b3J/Udp63+cyibpL4o4I6yPBTKAq8lco7hn4RgGsOY5tUa5qbHLZsmz eEPA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-language:content-transfer-encoding :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=QUdeFdKpjNEf8Hl81+BajO3ot7HfhtXSTnFIc/T0Nzw=; b=HgGbnBJk0lIl4i7i37isBEqw9j52ZTA9An+YmyK5zsAaFnWVT0Sd0EmEBuJRnM3dxf KhqqMN7LoGGR5yX9hFgdBOCJiIKg4W/dEC2fKpCBCvKUzKYNKRl8vJOnlbccwDz4ryEb Xjy5KG6Njp3w+ZEp38i9VNLOa9ZmxU+AjHxHj3fU0Snv6u/gtvdgjmM1oxa1BakcjI51 +7ouCgLGCInA6R+tFlVD91c2DDZm5giXwNDfWBWSl/mEWKO9wOduy3x3Y/mhSSFvgCsm ht+kALTxhFxEVgX5+jEg+o/zk8QF7XpUedVwFu0EL95gfiXa8hXkeJaUsy1f5pKBHdHP 96Ww== 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 Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id c14-20020a170902b68e00b001b04dd66179si8261874pls.274.2023.06.06.22.04.23; Tue, 06 Jun 2023 22:04:37 -0700 (PDT) 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234283AbjFGEdK (ORCPT + 99 others); Wed, 7 Jun 2023 00:33:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49488 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230086AbjFGEcd (ORCPT ); Wed, 7 Jun 2023 00:32:33 -0400 Received: from dggsgout12.his.huawei.com (unknown [45.249.212.56]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E19241FEC; Tue, 6 Jun 2023 21:30:45 -0700 (PDT) Received: from mail02.huawei.com (unknown [172.30.67.153]) by dggsgout12.his.huawei.com (SkyGuard) with ESMTP id 4QbYqX5904z4f3khb; Wed, 7 Jun 2023 12:13:28 +0800 (CST) Received: from [10.174.176.117] (unknown [10.174.176.117]) by APP1 (Coremail) with SMTP id cCh0CgAngRvkA4BkYN7+KQ--.51373S2; Wed, 07 Jun 2023 12:13:28 +0800 (CST) Subject: Re: [PATCH v4] blk-ioprio: Introduce promote-to-rt policy To: linux-block@vger.kernel.org, Jens Axboe Cc: Bart Van Assche , Jan Kara , Bagas Sanjaya , Chaitanya Kulkarni , cgroups@vger.kernel.org, Tejun Heo , Zefan Li , Johannes Weiner , Jonathan Corbet , linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, "houtao1@huawei.com" References: <20230428074404.280532-1-houtao@huaweicloud.com> <1db53a95-46d3-c906-31a1-0be4992a4b8d@huaweicloud.com> From: Hou Tao Message-ID: <116e9f61-cdf9-2eeb-51c3-a211bb1f06ca@huaweicloud.com> Date: Wed, 7 Jun 2023 12:13:24 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-CM-TRANSID: cCh0CgAngRvkA4BkYN7+KQ--.51373S2 X-Coremail-Antispam: 1UD129KBjvJXoW3GF1ftF1rWw43AF47GF18AFb_yoW3XF1DpF 4fAFW3uryvqF1xtF12q3WkXrW7t3s7tr17WFnxKFyF934qywnrAF1jyF18WFyxArWDXrZx Zr98AFZ2kFy5ZrJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUv2b4IE77IF4wAFF20E14v26r4j6ryUM7CY07I20VC2zVCF04k2 6cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rwA2F7IY1VAKz4 vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_Ar0_tr1l84ACjcxK6xIIjxv20xvEc7Cj xVAFwI0_Cr0_Gr1UM28EF7xvwVC2z280aVAFwI0_GcCE3s1l84ACjcxK6I8E87Iv6xkF7I 0E14v26rxl6s0DM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVACY4xI64kE6c02F40E x7xfMcIj6xIIjxv20xvE14v26r1j6r18McIj6I8E87Iv67AKxVWUJVW8JwAm72CE4IkC6x 0Yz7v_Jr0_Gr1lF7xvr2IY64vIr41lFIxGxcIEc7CjxVA2Y2ka0xkIwI1lc7I2V7IY0VAS 07AlzVAYIcxG8wCF04k20xvY0x0EwIxGrwCFx2IqxVCFs4IE7xkEbVWUJVW8JwC20s026c 02F40E14v26r1j6r18MI8I3I0E7480Y4vE14v26r106r1rMI8E67AF67kF1VAFwI0_Jw0_ GFylIxkGc2Ij64vIr41lIxAIcVC0I7IYx2IY67AKxVWUJVWUCwCI42IY6xIIjxv20xvEc7 CjxVAFwI0_Gr0_Cr1lIxAIcVCF04k26cxKx2IYs7xG6rW3Jr0E3s1lIxAIcVC2z280aVAF wI0_Jr0_Gr1lIxAIcVC2z280aVCY1x0267AKxVW8JVW8JrUvcSsGvfC2KfnxnUUI43ZEXa 7IU1zuWJUUUUU== X-CM-SenderInfo: xkrx3t3r6k3tpzhluzxrxghudrp/ X-CFilter-Loop: Reflected X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,KHOP_HELO_FCRDNS, NICE_REPLY_A,SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE 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 ping ? On 5/23/2023 2:48 PM, Hou Tao wrote: > ping ? > > On 5/8/2023 8:08 PM, Hou Tao wrote: >> ping ? >> >> On 4/28/2023 3:44 PM, Hou Tao wrote: >>> From: Hou Tao >>> >>> Since commit a78418e6a04c ("block: Always initialize bio IO priority on >>> submit"), bio->bi_ioprio will never be IOPRIO_CLASS_NONE when calling >>> blkcg_set_ioprio(), so there will be no way to promote the io-priority >>> of one cgroup to IOPRIO_CLASS_RT, because bi_ioprio will always be >>> greater than or equals to IOPRIO_CLASS_RT. >>> >>> It seems possible to call blkcg_set_ioprio() first then try to >>> initialize bi_ioprio later in bio_set_ioprio(), but this doesn't work >>> for bio in which bi_ioprio is already initialized (e.g., direct-io), so >>> introduce a new promote-to-rt policy to promote the iopriority of bio to >>> IOPRIO_CLASS_RT if the ioprio is not already RT. >>> >>> For none-to-rt policy, although it doesn't work now, but considering >>> that its purpose was also to override the io-priority to RT and allowing >>> for a smoother transition, just keep it and treat it as an alias of >>> the promote-to-rt policy. >>> >>> Acked-by: Tejun Heo >>> Reviewed-by: Bart Van Assche >>> Reviewed-by: Chaitanya Kulkarni >>> Reviewed-by: Jan Kara >>> Signed-off-by: Hou Tao >>> --- >>> v4: >>> * rebased on 33afd4b76393 >>> * Add Reviewed-by from Jan Kara >>> >>> v3: https://lore.kernel.org/linux-block/20230223135154.3749088-1-houtao@huaweicloud.com >>> * Use 'non-RT' instead of 'no-RT' in document (from Bagas) >>> * Remove repeated sentence in commit message >>> * Add Reviewed-by and Acked-by tags >>> >>> v2: https://lore.kernel.org/linux-block/20230220135428.2632906-1-houtao@huaweicloud.com >>> >>> * Simplify the implementation of promote-to-rt (from Bart) >>> * Make none-to-rt to work again by treating it as an alias of >>> the promote-to-rt policy (from Bart & Jan) >>> * fix the style of new content in cgroup-v2.rst (from Bagas) >>> * set the default priority level to 4 instead of 0 for promote-to-rt >>> >>> v1: https://lore.kernel.org/linux-block/20230201045227.2203123-1-houtao@huaweicloud.com >>> >>> Documentation/admin-guide/cgroup-v2.rst | 42 ++++++++++++++----------- >>> block/blk-ioprio.c | 23 ++++++++++++-- >>> 2 files changed, 44 insertions(+), 21 deletions(-) >>> >>> diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst >>> index f67c0829350b..7544ce00e0cb 100644 >>> --- a/Documentation/admin-guide/cgroup-v2.rst >>> +++ b/Documentation/admin-guide/cgroup-v2.rst >>> @@ -2024,31 +2024,33 @@ that attribute: >>> no-change >>> Do not modify the I/O priority class. >>> >>> - none-to-rt >>> - For requests that do not have an I/O priority class (NONE), >>> - change the I/O priority class into RT. Do not modify >>> - the I/O priority class of other requests. >>> + promote-to-rt >>> + For requests that have a non-RT I/O priority class, change it into RT. >>> + Also change the priority level of these requests to 4. Do not modify >>> + the I/O priority of requests that have priority class RT. >>> >>> restrict-to-be >>> For requests that do not have an I/O priority class or that have I/O >>> - priority class RT, change it into BE. Do not modify the I/O priority >>> - class of requests that have priority class IDLE. >>> + priority class RT, change it into BE. Also change the priority level >>> + of these requests to 0. Do not modify the I/O priority class of >>> + requests that have priority class IDLE. >>> >>> idle >>> Change the I/O priority class of all requests into IDLE, the lowest >>> I/O priority class. >>> >>> + none-to-rt >>> + Deprecated. Just an alias for promote-to-rt. >>> + >>> The following numerical values are associated with the I/O priority policies: >>> >>> -+-------------+---+ >>> -| no-change | 0 | >>> -+-------------+---+ >>> -| none-to-rt | 1 | >>> -+-------------+---+ >>> -| rt-to-be | 2 | >>> -+-------------+---+ >>> -| all-to-idle | 3 | >>> -+-------------+---+ >>> ++----------------+---+ >>> +| no-change | 0 | >>> ++----------------+---+ >>> +| rt-to-be | 2 | >>> ++----------------+---+ >>> +| all-to-idle | 3 | >>> ++----------------+---+ >>> >>> The numerical value that corresponds to each I/O priority class is as follows: >>> >>> @@ -2064,9 +2066,13 @@ The numerical value that corresponds to each I/O priority class is as follows: >>> >>> The algorithm to set the I/O priority class for a request is as follows: >>> >>> -- Translate the I/O priority class policy into a number. >>> -- Change the request I/O priority class into the maximum of the I/O priority >>> - class policy number and the numerical I/O priority class. >>> +- If I/O priority class policy is promote-to-rt, change the request I/O >>> + priority class to IOPRIO_CLASS_RT and change the request I/O priority >>> + level to 4. >>> +- If I/O priorityt class is not promote-to-rt, translate the I/O priority >>> + class policy into a number, then change the request I/O priority class >>> + into the maximum of the I/O priority class policy number and the numerical >>> + I/O priority class. >>> >>> PID >>> --- >>> diff --git a/block/blk-ioprio.c b/block/blk-ioprio.c >>> index 055529b9b92b..4051fada01f1 100644 >>> --- a/block/blk-ioprio.c >>> +++ b/block/blk-ioprio.c >>> @@ -23,25 +23,28 @@ >>> /** >>> * enum prio_policy - I/O priority class policy. >>> * @POLICY_NO_CHANGE: (default) do not modify the I/O priority class. >>> - * @POLICY_NONE_TO_RT: modify IOPRIO_CLASS_NONE into IOPRIO_CLASS_RT. >>> + * @POLICY_PROMOTE_TO_RT: modify no-IOPRIO_CLASS_RT to IOPRIO_CLASS_RT. >>> * @POLICY_RESTRICT_TO_BE: modify IOPRIO_CLASS_NONE and IOPRIO_CLASS_RT into >>> * IOPRIO_CLASS_BE. >>> * @POLICY_ALL_TO_IDLE: change the I/O priority class into IOPRIO_CLASS_IDLE. >>> + * @POLICY_NONE_TO_RT: an alias for POLICY_PROMOTE_TO_RT. >>> * >>> * See also . >>> */ >>> enum prio_policy { >>> POLICY_NO_CHANGE = 0, >>> - POLICY_NONE_TO_RT = 1, >>> + POLICY_PROMOTE_TO_RT = 1, >>> POLICY_RESTRICT_TO_BE = 2, >>> POLICY_ALL_TO_IDLE = 3, >>> + POLICY_NONE_TO_RT = 4, >>> }; >>> >>> static const char *policy_name[] = { >>> [POLICY_NO_CHANGE] = "no-change", >>> - [POLICY_NONE_TO_RT] = "none-to-rt", >>> + [POLICY_PROMOTE_TO_RT] = "promote-to-rt", >>> [POLICY_RESTRICT_TO_BE] = "restrict-to-be", >>> [POLICY_ALL_TO_IDLE] = "idle", >>> + [POLICY_NONE_TO_RT] = "none-to-rt", >>> }; >>> >>> static struct blkcg_policy ioprio_policy; >>> @@ -189,6 +192,20 @@ void blkcg_set_ioprio(struct bio *bio) >>> if (!blkcg || blkcg->prio_policy == POLICY_NO_CHANGE) >>> return; >>> >>> + if (blkcg->prio_policy == POLICY_PROMOTE_TO_RT || >>> + blkcg->prio_policy == POLICY_NONE_TO_RT) { >>> + /* >>> + * For RT threads, the default priority level is 4 because >>> + * task_nice is 0. By promoting non-RT io-priority to RT-class >>> + * and default level 4, those requests that are already >>> + * RT-class but need a higher io-priority can use ioprio_set() >>> + * to achieve this. >>> + */ >>> + if (IOPRIO_PRIO_CLASS(bio->bi_ioprio) != IOPRIO_CLASS_RT) >>> + bio->bi_ioprio = IOPRIO_PRIO_VALUE(IOPRIO_CLASS_RT, 4); >>> + return; >>> + } >>> + >>> /* >>> * Except for IOPRIO_CLASS_NONE, higher I/O priority numbers >>> * correspond to a lower priority. Hence, the max_t() below selects >> . > .