Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp1765397iog; Sat, 25 Jun 2022 19:41:44 -0700 (PDT) X-Google-Smtp-Source: AGRyM1v9NiAqlegS8G8ZvjTzYH+MwcI7o6rWHhbkdfPq/nRdNdy3N7gGXW7PD7b0xLiPHodZKYC0 X-Received: by 2002:a17:90a:77cc:b0:1ec:9bb5:3952 with SMTP id e12-20020a17090a77cc00b001ec9bb53952mr7866746pjs.111.1656211304549; Sat, 25 Jun 2022 19:41:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656211304; cv=none; d=google.com; s=arc-20160816; b=nAjlgLaACHSiOPG0JQsKUNmfEipPloyL8cK4VgrQHcQRUFlHTXTeqgoYrWUKLwbTKG t7+T1YgegifuFbIP6eZfHqows1ytPHr04pspoX/d8evZJagaaJBepU/OpTMUWs718zmR FSee67IfFNwXo1csUXmX+hWBYfhBpHXuJlgm9lOf6Jqs0xgNb+QSof3ITR67YnACq4lP hcT6z7R4ipEx9cni9dVGTRTw46AQwSQnBz5TILXm9oLSvfHPZ+P5s+nUAFW1nxXkS4kH EDBNt+P54LMp1vyEL1tugHwNO1WQoYylMszCONVMw6VfilDJ4JjeCZtWu/mXxiR1UJ1x 5mHQ== 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=tJOWbJBrsZ2MXHxBC2wsVnJLmzN9jDLS+6VL9053GI4=; b=SoABXkq3h31/5otHmcLiJrTba9PNAfCNfAoaFt1hiJvWDj/4PqMJ1iem517H121A4K cN9xBCa2LODEH5q6ApOrEtsFBDJaj1LffJv9lP9oJYXNTEVyso6LZrDRKE3dVRohAy9s Pu1K9hKHMEjmrya0ppl3MHrAA/7CYrdFTSkqdX3XobNaHvEYuvU0HbCjhTdvSH8LePoc LxMdVK1qJh97Z6ZBB0iPhvjIUJZeB613UI/MsuL7z/5kXcv3TH57yjh7ZoMiBoh4wAy9 OPynMiXlt6P3F0CG9GQmUoAXb+DHp33/75D6MK4uK54TQzJaahK+Y0V8FsfEogBAMEpj dDOQ== 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 e17-20020a170903241100b001542a6e4c9bsi8648299plo.485.2022.06.25.19.41.33; Sat, 25 Jun 2022 19:41:44 -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; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233707AbiFZCjw (ORCPT + 99 others); Sat, 25 Jun 2022 22:39:52 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49870 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232327AbiFZCjv (ORCPT ); Sat, 25 Jun 2022 22:39:51 -0400 Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [45.249.212.189]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7605712AC0; Sat, 25 Jun 2022 19:39:49 -0700 (PDT) Received: from dggemv703-chm.china.huawei.com (unknown [172.30.72.54]) by szxga03-in.huawei.com (SkyGuard) with ESMTP id 4LVw6Q2fbjzDsC8; Sun, 26 Jun 2022 10:39:10 +0800 (CST) Received: from kwepemm600009.china.huawei.com (7.193.23.164) by dggemv703-chm.china.huawei.com (10.3.19.46) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Sun, 26 Jun 2022 10:39:47 +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.2375.24; Sun, 26 Jun 2022 10:39:46 +0800 Subject: Re: [PATCH -next v5 4/8] blk-throttle: fix io hung due to config updates To: Jens Axboe , =?UTF-8?Q?Michal_Koutn=c3=bd?= , CC: , , , , References: <20220528064330.3471000-1-yukuai3@huawei.com> <20220528064330.3471000-5-yukuai3@huawei.com> <20220622172621.GA28246@blackbody.suse.cz> <20220623162620.GB16004@blackbody.suse.cz> <75b3cdcc-1aa3-7259-4900-f09a2a081716@huawei.com> <7e14a11b-225e-13c4-35ff-762eafd20b70@kernel.dk> From: Yu Kuai Message-ID: <65dac189-92f5-f2bc-b322-cbda10f897b4@huawei.com> Date: Sun, 26 Jun 2022 10:39:45 +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: <7e14a11b-225e-13c4-35ff-762eafd20b70@kernel.dk> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.174.176.73] X-ClientProxiedBy: dggems703-chm.china.huawei.com (10.3.19.180) To kwepemm600009.china.huawei.com (7.193.23.164) X-CFilter-Loop: Reflected X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_PASS,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 在 2022/06/26 0:41, Jens Axboe 写道: > On 6/25/22 2:36 AM, Yu Kuai wrote: >> ? 2022/06/24 0:26, Michal Koutn? ??: >>> On Thu, Jun 23, 2022 at 08:27:11PM +0800, Yu Kuai wrote: >>>>> Here we may allow to dispatch a bio above current slice's >>>>> calculate_bytes_allowed() if bytes_skipped is already >0. >>>> >>>> Hi, I don't expect that to happen. For example, if a bio is still >>>> throttled, then old slice is keeped with proper 'bytes_skipped', >>>> then new wait time is caculated based on (bio_size - bytes_skipped). >>>> >>>> After the bio is dispatched(I assum that other bios can't preempt), >>> >>> With this assumptions it adds up as you write. I believe we're in >>> agreement. >>> >>> It's the same assumption I made below (FIFO everywhere, i.e. no >>> reordering). So the discussed difference shouldn't really be negative >>> (and if the assumption didn't hold, so the modular arithmetic yields >>> corerct bytes_skipped value). >> Yes, nice that we're in aggreement. >> >> I'll wait to see if Tejun has any suggestions. > > I flushed more emails from spam again. Please stop using the buggy > huawei address until this gets resolved, your patches are getting lost > left and right and I don't have time to go hunting for emails. > My apologize for that, I'm quite annoied that our IT still can't solve this. I'll stop sending new emails with this address for now.. Thanks, Kuai