From: Yu Kuai <yukuai3@huawei.com>
To: <tj@kernel.org>, <axboe@kernel.dk>, <ming.lei@redhat.com>
Cc: <cgroups@vger.kernel.org>, <linux-block@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <yukuai3@huawei.com>,
<yi.zhang@huawei.com>
Subject: [PATCH -next v2 0/2] bugfix for blk-throttle
Date: Wed, 18 May 2022 15:27:49 +0800 [thread overview]
Message-ID: <20220518072751.1188163-1-yukuai3@huawei.com> (raw)
Changes in v2:
- use a new solution suggested by Ming
- change the title of patch 1
- add patch 2
Patch 1 fix that blk-throttle can't work if multiple bios are throttle,
Patch 2 fix io hung due to configuration updates.
Previous version:
v1 : https://lore.kernel.org/all/20220517134909.2910251-1-yukuai3@huawei.com/
Yu Kuai (2):
blk-throttle: fix that io throttle can only work for single bio
blk-throttle: fix io hung due to configuration updates
block/blk-throttle.c | 88 ++++++++++++++++++++++++++++++++++----------
1 file changed, 69 insertions(+), 19 deletions(-)
--
2.31.1
WARNING: multiple messages have this Message-ID (diff)
From: Yu Kuai <yukuai3-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org,
ming.lei-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
yukuai3-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
yi.zhang-hv44wF8Li93QT0dZR+AlfA@public.gmane.org
Subject: [PATCH -next v2 0/2] bugfix for blk-throttle
Date: Wed, 18 May 2022 15:27:49 +0800 [thread overview]
Message-ID: <20220518072751.1188163-1-yukuai3@huawei.com> (raw)
Changes in v2:
- use a new solution suggested by Ming
- change the title of patch 1
- add patch 2
Patch 1 fix that blk-throttle can't work if multiple bios are throttle,
Patch 2 fix io hung due to configuration updates.
Previous version:
v1 : https://lore.kernel.org/all/20220517134909.2910251-1-yukuai3-hv44wF8Li93QT0dZR+AlfA@public.gmane.org/
Yu Kuai (2):
blk-throttle: fix that io throttle can only work for single bio
blk-throttle: fix io hung due to configuration updates
block/blk-throttle.c | 88 ++++++++++++++++++++++++++++++++++----------
1 file changed, 69 insertions(+), 19 deletions(-)
--
2.31.1
next reply other threads:[~2022-05-18 7:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 7:27 Yu Kuai [this message]
2022-05-18 7:27 ` [PATCH -next v2 0/2] bugfix for blk-throttle Yu Kuai
2022-05-18 7:27 ` [PATCH -next v2 1/2] blk-throttle: fix that io throttle can only work for single bio Yu Kuai
2022-05-18 7:27 ` Yu Kuai
2022-05-18 9:50 ` Ming Lei
2022-05-18 7:27 ` [PATCH -next v2 2/2] blk-throttle: fix io hung due to configuration updates Yu Kuai
2022-05-18 7:27 ` Yu Kuai
2022-05-18 15:52 ` kernel test robot
2022-05-18 15:52 ` kernel test robot
2022-05-19 2:11 ` yukuai (C)
2022-05-19 2:11 ` yukuai (C)
2022-05-19 2:11 ` yukuai
2022-05-19 3:01 ` yukuai (C)
2022-05-19 3:01 ` yukuai (C)
2022-05-19 3:01 ` yukuai
2022-05-19 7:01 ` Geert Uytterhoeven
2022-05-19 7:01 ` Geert Uytterhoeven
2022-05-19 7:06 ` yukuai (C)
2022-05-19 7:06 ` yukuai (C)
2022-05-19 7:06 ` yukuai
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=20220518072751.1188163-1-yukuai3@huawei.com \
--to=yukuai3@huawei.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=tj@kernel.org \
--cc=yi.zhang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.