From: Yu Kuai <yukuai1@huaweicloud.com>
To: tj@kernel.org, hch@infradead.org, josef@toxicpanda.com, axboe@kernel.dk
Cc: cgroups@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, yukuai3@huawei.com,
yukuai1@huaweicloud.com, yi.zhang@huawei.com
Subject: [PATCH v2 0/2] blk-iocost: add refcounting for iocg and ioc
Date: Tue, 27 Dec 2022 20:55:00 +0800 [thread overview]
Message-ID: <20221227125502.541931-1-yukuai1@huaweicloud.com> (raw)
From: Yu Kuai <yukuai3@huawei.com>
Changes in v2:
- Instead add ioc_pd_offline(), and move operations for iocg from
ioc_pd_free() to ioc_pd_offline(), use refcounting to fix the problem.
Yu Kuai (2):
blk-iocost: add refcounting for iocg
blk-iocost: add refcounting for ioc
block/blk-iocost.c | 86 ++++++++++++++++++++++++++++++++--------------
1 file changed, 61 insertions(+), 25 deletions(-)
--
2.31.1
next reply other threads:[~2022-12-27 12:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 12:55 Yu Kuai [this message]
2022-12-27 12:55 ` [PATCH v2 1/2] blk-iocost: add refcounting for iocg Yu Kuai
2023-01-04 21:44 ` Tejun Heo
2023-01-05 1:14 ` Yu Kuai
2023-01-05 18:32 ` Tejun Heo
2023-01-06 1:08 ` Yu Kuai
2023-01-06 20:18 ` Tejun Heo
2023-01-09 1:32 ` Yu Kuai
2023-01-09 18:23 ` Tejun Heo
2023-01-10 1:39 ` Yu Kuai
2023-01-10 18:36 ` Tejun Heo
2023-01-11 1:36 ` Yu Kuai
2023-01-11 17:07 ` Tejun Heo
2023-01-12 6:18 ` Yu Kuai
2023-01-13 0:53 ` Tejun Heo
2023-01-13 1:10 ` Yu Kuai
2023-01-13 1:15 ` Tejun Heo
2023-01-13 1:25 ` Yu Kuai
2023-01-13 17:16 ` Tejun Heo
2023-01-16 3:25 ` Yu Kuai
2022-12-27 12:55 ` [PATCH v2 2/2] blk-iocost: add refcounting for ioc Yu Kuai
2023-01-04 21:45 ` Tejun Heo
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=20221227125502.541931-1-yukuai1@huaweicloud.com \
--to=yukuai1@huaweicloud.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=hch@infradead.org \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--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).