Message ID | 20230512093554.911753-1-yukuai1@huaweicloud.com |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:b0ea:0:b0:3b6:4342:cba0 with SMTP id b10csp4969299vqo; Fri, 12 May 2023 02:42:35 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ5tETg8Hb6P043oyNECn5NZ4nUBvMTC9M/AZwoVfTv6PiGcj0E+TH2rUPNK1SEIOL9fi0fH X-Received: by 2002:a05:6a21:3386:b0:101:241d:55fe with SMTP id yy6-20020a056a21338600b00101241d55femr19198326pzb.45.1683884555522; Fri, 12 May 2023 02:42:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683884555; cv=none; d=google.com; s=arc-20160816; b=cThnfaFnW7xkEbjfpZQD2xt92hImNI2aMm93s13MuA4N3qwhMn5rg9/TebkayEAISR +HsKvsjYubJcPYlA7JcZbiV7q/UtKBp3I1wbIVkd1pX9GLFbsCXT6IijlM6m6kX+o8Kl f3ztiEDfEaC9+G3OSQPJzrMFkxgIiNWos5eolvBNKgCpPsUZdIUIS2KZqTW+VGFiNbu8 bVgCas4Nns/jSo1Gj5I+gYY1ivxybXIVktBmr8yVVBgyxM1PjupVHtv2PMrQNS7RAWJS y2GDr0/kyCOX+id3hDOdtdCcqsDrDLr8l82xX5jm8r+67Jamb8Y0IH5rhRmtwcSAujaa 3vUA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from; bh=0zQUzcdL8RzlJ1PqbxC3p/PUDAGvJHeoM/dAiRtUBUQ=; b=Gt56BTv8unjsPB6r7zvqZ0hBPlbiFOixAUX7UP2spxtGr2jCBdT5nNRylz6wuj0AjY y0OZwPTJ38xGmgJd85dgPsec4519NFsZw+9yNcahZxQqCgl9ptUWJ8JkE17Otz3fBmWP elfNu5frjdRyy2NNpyxCt5i2Nlf5cjKa2ZrWc/VZJz7LF0vR46O2zDS6pv93hD/JPrsf sJW/Is4Wmn3MPExjm0qNb79xILPOTKfxAB8LkE/e3yYk8jhNtJ3HITx6Om4T/UVf/k6Q h0sDo5DpbBBq77n7UnaJng09cechj4N5PmKCYeDbt25ccstDsVdNTwpWvNmNDr5XxOE9 qA1A== 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 Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id p6-20020a625b06000000b00643b4d12e48si9749174pfb.125.2023.05.12.02.42.21; Fri, 12 May 2023 02:42:35 -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 S240356AbjELJim (ORCPT <rfc822;peekingduck44@gmail.com> + 99 others); Fri, 12 May 2023 05:38:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35182 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239740AbjELJil (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Fri, 12 May 2023 05:38:41 -0400 Received: from dggsgout11.his.huawei.com (dggsgout11.his.huawei.com [45.249.212.51]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6C4E410A23; Fri, 12 May 2023 02:38:39 -0700 (PDT) Received: from mail02.huawei.com (unknown [172.30.67.143]) by dggsgout11.his.huawei.com (SkyGuard) with ESMTP id 4QHkGf2H6kz4f3wt3; Fri, 12 May 2023 17:38:34 +0800 (CST) Received: from huaweicloud.com (unknown [10.175.104.67]) by APP2 (Coremail) with SMTP id Syh0CgA33eoZCV5k66u5JA--.8346S4; Fri, 12 May 2023 17:38:35 +0800 (CST) From: Yu Kuai <yukuai1@huaweicloud.com> To: hch@lst.de, tj@kernel.org, josef@toxicpanda.com, axboe@kernel.dk, yukuai3@huawei.com Cc: lukas.bulwahn@gmail.com, cgroups@vger.kernel.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, yukuai1@huaweicloud.com, yi.zhang@huawei.com, yangerkun@huawei.com Subject: [PATCH -next v2 0/6] blk-wbt: minor fix and cleanup Date: Fri, 12 May 2023 17:35:48 +0800 Message-Id: <20230512093554.911753-1-yukuai1@huaweicloud.com> X-Mailer: git-send-email 2.39.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-CM-TRANSID: Syh0CgA33eoZCV5k66u5JA--.8346S4 X-Coremail-Antispam: 1UD129KBjvdXoWrtrWrWF1DZFWfWw1DuFW7Arb_yoW3uwb_WF 9rJaykX3Z8ZFZ3CFy2kF15XFWUKr4rZrWjvF95XrWayry3JFyDKw4ktrsxXrW3ZF4xKFyY qr1UWr48Jr18tjkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUbxAFF20E14v26r4j6ryUM7CY07I20VC2zVCF04k26cxKx2IYs7xG 6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rwA2F7IY1VAKz4vEj48ve4kI8w A2z4x0Y4vE2Ix0cI8IcVAFwI0_tr0E3s1l84ACjcxK6xIIjxv20xvEc7CjxVAFwI0_Gr1j 6F4UJwA2z4x0Y4vEx4A2jsIE14v26rxl6s0DM28EF7xvwVC2z280aVCY1x0267AKxVW0oV Cq3wAS0I0E0xvYzxvE52x082IY62kv0487Mc02F40EFcxC0VAKzVAqx4xG6I80ewAv7VC0 I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lOx8S6xCaFVCjc4AY6r1j6r 4UM4x0Y48IcxkI7VAKI48JM4x0x7Aq67IIx4CEVc8vx2IErcIFxwACI402YVCY1x02628v n2kIc2xKxwCF04k20xvY0x0EwIxGrwCFx2IqxVCFs4IE7xkEbVWUJVW8JwC20s026c02F4 0E14v26r1j6r18MI8I3I0E7480Y4vE14v26r106r1rMI8E67AF67kF1VAFwI0_Jw0_GFyl IxkGc2Ij64vIr41lIxAIcVC0I7IYx2IY67AKxVWUJVWUCwCI42IY6xIIjxv20xvEc7CjxV AFwI0_Gr0_Cr1lIxAIcVCF04k26cxKx2IYs7xG6rW3Jr0E3s1lIxAIcVC2z280aVAFwI0_ Gr0_Cr1lIxAIcVC2z280aVCY1x0267AKxVW8Jr0_Cr1UYxBIdaVFxhVjvjDU0xZFpf9x0J UdHUDUUUUU= X-CM-SenderInfo: 51xn3trlr6x35dzhxuhorxvhhfrp/ X-CFilter-Loop: Reflected X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,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: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1765680931435782582?= X-GMAIL-MSGID: =?utf-8?q?1765680931435782582?= |
Series |
blk-wbt: minor fix and cleanup
|
|
Message
Yu Kuai
May 12, 2023, 9:35 a.m. UTC
From: Yu Kuai <yukuai3@huawei.com>
Changes in v2:
- make the code more readable for patch 1
- add a new attr_group that is only visible for rq based device
- explain in detail for patch 4
- add review tag for patch 2,3,5
Yu Kuai (6):
blk-wbt: fix that wbt can't be disabled by default
blk-wbt: don't create wbt sysfs entry if CONFIG_BLK_WBT is disabled
blk-wbt: remove dead code to handle wbt enable/disable with io
inflight
blk-wbt: cleanup rwb_enabled() and wbt_disabled()
blk-iocost: move wbt_enable/disable_default() out of spinlock
blk-sysfs: add a new attr_group for blk_mq
block/blk-iocost.c | 7 +-
block/blk-sysfs.c | 181 ++++++++++++++++++++++++++-------------------
block/blk-wbt.c | 33 +++------
block/blk-wbt.h | 19 -----
4 files changed, 117 insertions(+), 123 deletions(-)
Comments
On 5/12/23 3:35 AM, Yu Kuai wrote: > From: Yu Kuai <yukuai3@huawei.com> > > Changes in v2: > - make the code more readable for patch 1 > - add a new attr_group that is only visible for rq based device > - explain in detail for patch 4 > - add review tag for patch 2,3,5 > > Yu Kuai (6): > blk-wbt: fix that wbt can't be disabled by default > blk-wbt: don't create wbt sysfs entry if CONFIG_BLK_WBT is disabled > blk-wbt: remove dead code to handle wbt enable/disable with io > inflight > blk-wbt: cleanup rwb_enabled() and wbt_disabled() > blk-iocost: move wbt_enable/disable_default() out of spinlock > blk-sysfs: add a new attr_group for blk_mq > > block/blk-iocost.c | 7 +- > block/blk-sysfs.c | 181 ++++++++++++++++++++++++++------------------- > block/blk-wbt.c | 33 +++------ > block/blk-wbt.h | 19 ----- > 4 files changed, 117 insertions(+), 123 deletions(-) We need a 6.4 version of the fix to get rid of the regression. If you want to do cleanups on top of that, then that's fine and that can go into 6.5. But don't mix them up.
On 12.05.23 16:58, Jens Axboe wrote: > On 5/12/23 3:35 AM, Yu Kuai wrote: >> From: Yu Kuai <yukuai3@huawei.com> >> >> Changes in v2: >> - make the code more readable for patch 1 >> - add a new attr_group that is only visible for rq based device >> - explain in detail for patch 4 >> - add review tag for patch 2,3,5 >> >> Yu Kuai (6): >> blk-wbt: fix that wbt can't be disabled by default >> blk-wbt: don't create wbt sysfs entry if CONFIG_BLK_WBT is disabled >> blk-wbt: remove dead code to handle wbt enable/disable with io >> inflight >> blk-wbt: cleanup rwb_enabled() and wbt_disabled() >> blk-iocost: move wbt_enable/disable_default() out of spinlock >> blk-sysfs: add a new attr_group for blk_mq >> >> block/blk-iocost.c | 7 +- >> block/blk-sysfs.c | 181 ++++++++++++++++++++++++++------------------- >> block/blk-wbt.c | 33 +++------ >> block/blk-wbt.h | 19 ----- >> 4 files changed, 117 insertions(+), 123 deletions(-) > > We need a 6.4 version of the fix to get rid of the regression. If you > want to do cleanups on top of that, then that's fine and that can go into > 6.5. But don't mix them up. Hmm, it seems nothing has happened here since ten days to fix this regression that likely is still present in 6.3. Yu Kuai, did it fall through the cracks, or is what Jens asked for more complicated than it sounds? Or was progress made and I just missed it? Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr If I did something stupid, please tell me, as explained on that page. #regzbot poke
Hi, 在 2023/05/22 20:00, Linux regression tracking (Thorsten Leemhuis) 写道: > On 12.05.23 16:58, Jens Axboe wrote: >> On 5/12/23 3:35 AM, Yu Kuai wrote: >>> From: Yu Kuai <yukuai3@huawei.com> >>> >>> Changes in v2: >>> - make the code more readable for patch 1 >>> - add a new attr_group that is only visible for rq based device >>> - explain in detail for patch 4 >>> - add review tag for patch 2,3,5 >>> >>> Yu Kuai (6): >>> blk-wbt: fix that wbt can't be disabled by default >>> blk-wbt: don't create wbt sysfs entry if CONFIG_BLK_WBT is disabled >>> blk-wbt: remove dead code to handle wbt enable/disable with io >>> inflight >>> blk-wbt: cleanup rwb_enabled() and wbt_disabled() >>> blk-iocost: move wbt_enable/disable_default() out of spinlock >>> blk-sysfs: add a new attr_group for blk_mq >>> >>> block/blk-iocost.c | 7 +- >>> block/blk-sysfs.c | 181 ++++++++++++++++++++++++++------------------- >>> block/blk-wbt.c | 33 +++------ >>> block/blk-wbt.h | 19 ----- >>> 4 files changed, 117 insertions(+), 123 deletions(-) >> >> We need a 6.4 version of the fix to get rid of the regression. If you >> want to do cleanups on top of that, then that's fine and that can go into >> 6.5. But don't mix them up. > > Hmm, it seems nothing has happened here since ten days to fix this > regression that likely is still present in 6.3. Yu Kuai, did it fall > through the cracks, or is what Jens asked for more complicated than it > sounds? Sorry for the delay, I was waiting for the last patch to be reviewed. But the regression is only related to the first patch, I'll send it seperately. Thanks, Kuai > > Or was progress made and I just missed it? > > Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) > -- > Everything you wanna know about Linux kernel regression tracking: > https://linux-regtracking.leemhuis.info/about/#tldr > If I did something stupid, please tell me, as explained on that page. > > #regzbot poke > > . >