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;
From:   Jens Axboe <axboe@kernel.dk>
To:     bvanassche@acm.org, Zhiguo Niu <zhiguo.niu@unisoc.com>
Cc:     linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
        niuzhiguo84@gmail.com, hongyu.jin@unisoc.com,
        yunlong.xing@unisoc.com
In-Reply-To: <1691061162-22898-1-git-send-email-zhiguo.niu@unisoc.com>
References: <1691061162-22898-1-git-send-email-zhiguo.niu@unisoc.com>
Subject: Re: [PATCH] block/mq-deadline: use correct way to throttling write
 requests
Message-Id: <169153121035.141127.745815954316396191.b4-ty@kernel.dk>
Date:   Tue, 08 Aug 2023 15:46:50 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk


On Thu, 03 Aug 2023 19:12:42 +0800, Zhiguo Niu wrote:
> The original formula was inaccurate:
> dd->async_depth = max(1UL, 3 * q->nr_requests / 4);
> 
> For write requests, when we assign a tags from sched_tags,
> data->shallow_depth will be passed to sbitmap_find_bit,
> see the following code:
> 
> [...]

Applied, thanks!

[1/1] block/mq-deadline: use correct way to throttling write requests
      commit: d47f9717e5cfd0dd8c0ba2ecfa47c38d140f1bb6

Best regards,
-- 
Jens Axboe