From: Tejun Heo <tj@kernel.org>
To: "yukuai (C)" <yukuai3@huawei.com>
Cc: "Michal Koutný" <mkoutny@suse.com>,
axboe@kernel.dk, ming.lei@redhat.com, geert@linux-m68k.org,
cgroups@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com
Subject: Re: [PATCH -next v3 2/2] blk-throttle: fix io hung due to configuration updates
Date: Fri, 20 May 2022 19:00:15 -1000 [thread overview]
Message-ID: <Yohx305S2bkSemQx@slm.duckdns.org> (raw)
In-Reply-To: <97be6af0-ea94-f4ee-5ab2-02b6fc02cbff@huawei.com>
On Sat, May 21, 2022 at 11:51:11AM +0800, yukuai (C) wrote:
> It's right the problem is self-inflicted. However, I do think with
> Michal's suggestion, how throttled bios are handled while new config is
> submitted really make sense from the functional poinit of view.
>
> Do you think the solution is OK?
I haven't followed the details but anything which isn't overly complex and
doesn't produce extra budget or eat into existing one on config change is
fine by me.
Thanks.
--
tejun
next prev parent reply other threads:[~2022-05-21 5:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 8:58 [PATCH -next v3 0/2] bugfix for blk-throttle Yu Kuai
2022-05-19 8:58 ` [PATCH -next v3 1/2] blk-throttle: fix that io throttle can only work for single bio Yu Kuai
2022-05-19 10:42 ` Ming Lei
2022-05-19 8:58 ` [PATCH -next v3 2/2] blk-throttle: fix io hung due to configuration updates Yu Kuai
2022-05-19 9:58 ` Michal Koutný
2022-05-19 12:14 ` yukuai (C)
2022-05-19 16:10 ` Michal Koutný
2022-05-20 1:22 ` yukuai (C)
2022-05-20 1:36 ` yukuai (C)
2022-05-20 16:03 ` Michal Koutný
2022-05-20 16:20 ` Tejun Heo
2022-05-21 3:51 ` yukuai (C)
2022-05-21 5:00 ` Tejun Heo [this message]
2022-05-21 3:01 ` yukuai (C)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yohx305S2bkSemQx@slm.duckdns.org \
--to=tj@kernel.org \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=mkoutny@suse.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).