Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp1785422pxb; Wed, 9 Feb 2022 04:34:38 -0800 (PST) X-Google-Smtp-Source: ABdhPJyxXmCVAZKmlBbm/x62PJwBW60fIlICdp2eXM/L1TIj08aqDtR+rvrAAYK8GkE1c0qdV+PJ X-Received: by 2002:aa7:8745:: with SMTP id g5mr2073397pfo.1.1644410078553; Wed, 09 Feb 2022 04:34:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1644410078; cv=none; d=google.com; s=arc-20160816; b=jonuScpgUgro+4qXJRvY1oJ3stTzSEJTwQzOkB8CeGHQqYeWnTSqY8o7cNJBYu8XNy RquuhB8bzD7b7Sqtxt64/9sOSEAZo+2h57ra0wSdcUlCM2KWIeJAHf2lqYP4o9kPm1+v v9ukusbd5q73BOOtiNoMW/ne/XjTr+4GifE1mp5VPlrRhbVJIavmJUPA4DCW8sycA2ve 6CX4KWRtNIzjFBc5VmqZJnXfizp+YaoXBzZZZSKIZR8D22w9JjKCAGA9aODBVj8KCqhw /8FlnuaENgBiaG7+dH1IfnUwSBQ8WKmoGkjOLB8/xjV2S4SCR1+GfzPHnbI/5ifNjg8V 7ksg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:references:cc:to :subject; bh=lVpXTEVeLUAzfGQzhgr8F+Kia5ZvRqy/EXObjHdbJYo=; b=uV1edHm+SKD/yJoe3OPBOTcU63DvOUdAN65DWQS6XKqnYjk6gAGWzB+Vzgiuxc+QTa a7VcSBuzkMmc5K2YztyM0c2tgmvArXT7JILJyRuAYoxJWiQPSLTozs/83DN9HaWlhXJL YGrdHnE77r9EGAuh2Mb4asyOhhHga5pd0jhNvBA0fiRea4v1MDqEYOY2w+wZ8OiyJ3jo inoGqS71e8Hxq9LgrBLaxKcnyGAAK+CkjLRHaBcNAI12CbxP6mkl8w7/KyY/oen0s819 9W4l40CEa9VrRJRICFrkf+Ewk9W9ocU9WFXmGZU54AUGI4SjBZzRJuhAKL6Iqj4j8yUL +eDQ== 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:18 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 lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id v9si16969921pfu.239.2022.02.09.04.34.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 09 Feb 2022 04:34:38 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 77512E13B01E; Wed, 9 Feb 2022 02:22:29 -0800 (PST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242639AbiBICqX (ORCPT + 99 others); Tue, 8 Feb 2022 21:46:23 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53042 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239601AbiBIBWf (ORCPT ); Tue, 8 Feb 2022 20:22:35 -0500 Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D254FC061576; Tue, 8 Feb 2022 17:22:33 -0800 (PST) Received: from kwepemi100004.china.huawei.com (unknown [172.30.72.54]) by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4JthsS3FqNz9sNn; Wed, 9 Feb 2022 09:21:00 +0800 (CST) Received: from kwepemm600009.china.huawei.com (7.193.23.164) by kwepemi100004.china.huawei.com (7.221.188.70) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Wed, 9 Feb 2022 09:22:31 +0800 Received: from [10.174.176.73] (10.174.176.73) by kwepemm600009.china.huawei.com (7.193.23.164) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Wed, 9 Feb 2022 09:22:30 +0800 Subject: Re: [PATCH -next] blk-throttle: enable io throttle for root in cgroup v2 To: Tejun Heo CC: , , , , References: <20220114093000.3323470-1-yukuai3@huawei.com> <235b0757-d322-2b6e-3ab6-ecc8c82f8f1e@huawei.com> <32b6949d-60b1-82ce-ae44-1cf089a78276@huawei.com> From: "yukuai (C)" Message-ID: <34ae7d06-4f6b-73f7-7299-65cb8859aad8@huawei.com> Date: Wed, 9 Feb 2022 09:22:30 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="gbk"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.174.176.73] X-ClientProxiedBy: dggems705-chm.china.huawei.com (10.3.19.182) To kwepemm600009.china.huawei.com (7.193.23.164) X-CFilter-Loop: Reflected X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A, RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no 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 ?? 2022/02/09 2:49, Tejun Heo ะด??: > Hello, > > On Tue, Feb 08, 2022 at 09:38:33AM +0800, yukuai (C) wrote: >> 3) If we limit iops to 8 for each client from server, client should work >> fine, however, server can receive 64 x 8 = 512 io at most at the same >> time, which might cause too much pressure on the server.(maybe bps is >> more appropriate to explain the high pressure). > > I don't follow this part. Why can't the server control however it wanna > control? Hi, Do you agree that the server can't control how many io it can receives from one client if we limit from server? I think the difference is that limit from client can control it... Thanks, Kuai > > Thanks. >