Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp2442288rwb; Sat, 24 Sep 2022 08:23:22 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4JTCeDkxFNLGyNQnKZhYaD1QaP764c11c6My3htCvgzOTTrQqEuyI+T6c5DOzy2i21i7Mm X-Received: by 2002:a17:90b:4b4b:b0:203:6733:2d1b with SMTP id mi11-20020a17090b4b4b00b0020367332d1bmr15892732pjb.82.1664033002141; Sat, 24 Sep 2022 08:23:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1664033002; cv=none; d=google.com; s=arc-20160816; b=EKfKa6AdjOQ6HyDvkWohfO38CoRB6chHMRRwuhHfKAPlBfLceMqWs54UsxXYnSWR4t Sy2Hd/plNzmmL3WTcKmL7/bT93Wb1KUesHJUbF8SUsObpI+rASG+EKQSphX+jR9FsxZf MuG200xoQBWwhe2YN1+gE1CkbpCKbIqKlwdkDUPfUQKbD5ZgMfU7Fsl44jHQMPMAkX9F raiAbQEo0BeXnD0rfLXscSva4vstm3SLzsh3PhonwBOeaekDomZMQFFrzhgmnSjt1LXB cO+7oCKHLqd2lgzY2xVCgUKzmYmFzIzThAdDpO07lg7DAoQvJsjS7Xa9Wzps24JJomm4 7qJQ== 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:date :message-id:subject:references:in-reply-to:cc:to:from:dkim-signature; bh=/ZxmoZGavmWNlrZnawkbXveh01Wn367vmE/VNkXmIdw=; b=mpdfV+DAicDxPqPidmYQM6KyJd5eL1bFSxRt7ZvAI1LhCkYJWvyQW9AsM1ISw0VJMM 734PxkuGdeaarN6MDB2WA3Fwrex4fNAFmISozwOjBPQGix5+jySvI03f5VDRtFfcjAsx bHV6Uw0IenrJllDn7uszds0dAUodENAOH2kS/WWSlpKwAnWKJmdHKC04z030wfzHReXl Zu4u8T0nHMcUu9icexkAQiDfn6s8y+1wMUm2oH+eBDpFs4EYb1aldmyE7PJP6QsfxWqx 3wWm4TzxhUiwcmJZqotq4Os8NYx+vGgbSkmRz41dmNC9P9RWr76Jyrge8vto4aId+lRZ pm+A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel-dk.20210112.gappssmtp.com header.s=20210112 header.b=s25ZCs1t; 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 s13-20020a170902988d00b00172c1c6abc1si6258505plp.172.2022.09.24.08.23.10; Sat, 24 Sep 2022 08:23:22 -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; dkim=pass header.i=@kernel-dk.20210112.gappssmtp.com header.s=20210112 header.b=s25ZCs1t; 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 S230111AbiIXPAP (ORCPT + 99 others); Sat, 24 Sep 2022 11:00:15 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45050 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229495AbiIXPAN (ORCPT ); Sat, 24 Sep 2022 11:00:13 -0400 Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 66F49B41 for ; Sat, 24 Sep 2022 08:00:12 -0700 (PDT) Received: by mail-pg1-x533.google.com with SMTP id e67so2781664pgc.12 for ; Sat, 24 Sep 2022 08:00:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:mime-version:date:message-id:subject :references:in-reply-to:cc:to:from:from:to:cc:subject:date; bh=/ZxmoZGavmWNlrZnawkbXveh01Wn367vmE/VNkXmIdw=; b=s25ZCs1tSDwZADqqqf1Vm4xt2zv7eMrlkQYv4xQaqPF3mPJzzvhB2mzxAqxPkb32pK NHAqqy/qx4pNcfeO5zqFmmWF2ufBVP1cOVbbxVTdLQvPTSHxLDM+xweoWGa34eoy6rDG dyyruF1ntIIDA6CvCIvQDTZADmji0DJAHX5s0Vhfrhdfq4gt11Qo5ttrdt7FnYlOgmiM g8G3lY1JxPY4sBzH8MwvY9x6UDIuc8ekZ8AqGfJh5wk+r/EmtPVkEnjYkiP/kHjK9ETv OYDkJBXcuZFyiUKv4Aw+s8K/uMug7rbzVAcHajZOqT5eH86LKpfotHSrJsWWt7a+AOji zcSA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:date:message-id:subject :references:in-reply-to:cc:to:from:x-gm-message-state:from:to:cc :subject:date; bh=/ZxmoZGavmWNlrZnawkbXveh01Wn367vmE/VNkXmIdw=; b=f8i1W0fmlvreQ7nfn9ncPfAukOfkMQPKLzyeRMWVP/c0twKG8td5G51iWJ+Lo5bI7L C8qgd2icVb573mEoVyCnCex7OwG+V41LqVYz7AaYkLlm4zqfjfNUmyPlABvBaKOTTGeM //fkLdKsiGcj0ENfix91qYhUFmj/LEcTeaZ4xFMMqWtga4JV6Bu+S0zOf+Bmt0P+uJuV kcQNqM5I8/StzIqbTluXVKtu/WrlWYDauLyq+UP1qElDq5XuGW5QyPB/HrdxhEw9hTxY XHMvALKCza9+Y2xILiSYVNElbmc3FXLljiPY85hxUdXJ2/09EgqjSjQ2TIoH6dNefcQp jm7g== X-Gm-Message-State: ACrzQf1XZYrFntyk60DHI5DzhMl/Os39XidJoNnkA8ugy+CkWlgc7qnx GVa2lS08J/9RykRNbvxnLBCOiA== X-Received: by 2002:a63:5d48:0:b0:43a:390b:2183 with SMTP id o8-20020a635d48000000b0043a390b2183mr12204841pgm.29.1664031611841; Sat, 24 Sep 2022 08:00:11 -0700 (PDT) Received: from [127.0.0.1] ([198.8.77.157]) by smtp.gmail.com with ESMTPSA id k1-20020a170902760100b0017870f471f6sm7848200pll.226.2022.09.24.08.00.10 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 24 Sep 2022 08:00:11 -0700 (PDT) From: Jens Axboe To: tj@kernel.org, Yu Kuai Cc: linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, linux-block@vger.kernel.org, yi.zhang@huawei.com, yukuai3@huawei.com In-Reply-To: <20220921095309.1481289-1-yukuai1@huaweicloud.com> References: <20220921095309.1481289-1-yukuai1@huaweicloud.com> Subject: Re: [PATCH 0/2] blk-throttle: improve bypassing bios checkings Message-Id: <166403161084.5171.274436515046613194.b4-ty@kernel.dk> Date: Sat, 24 Sep 2022 09:00:10 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Mailer: b4 0.10.0-dev-355bd X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,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 Wed, 21 Sep 2022 17:53:07 +0800, Yu Kuai wrote: > From: Yu Kuai > > Currently, "tg->has_rules" and "tg->flags & THROTL_TG_HAS_IOPS_LIMIT" > both try to bypass bios that don't need to be throttled, however, they are > a little redundant and both not perfect: > > 1) "tg->has_rules" only distinguish read and write, but not iops and bps > limit. > 2) "tg->flags & THROTL_TG_HAS_IOPS_LIMIT" only check if iops limit > exist, read and write is not distinguished, and bps limit is not > checked. > > [...] Applied, thanks! [1/2] blk-throttle: remove THROTL_TG_HAS_IOPS_LIMIT commit: 85496749904016f36b69332f73a1cf3ecfee828f [2/2] blk-throttle: improve bypassing bios checkings commit: 81c7a63abc7c0be572b4f853e913ce93a34f6e1b Best regards, -- Jens Axboe