From: Yu Kuai <yukuai1@huaweicloud.com>
To: axboe@kernel.dk, chenhuacai@kernel.org, tj@kernel.org,
josef@toxicpanda.com, victor@mojatatu.com, raven@themaw.net,
yukuai3@huawei.com, twoerner@gmail.com, zhaotianrui@loongson.cn,
svenjoac@gmx.de, jhs@mojatatu.com
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
loongarch@lists.linux.dev, cgroups@vger.kernel.org,
yukuai1@huaweicloud.com, yi.zhang@huawei.com,
yangerkun@huawei.com
Subject: [PATCH for-6.10/block 0/2] blk-throtl: delete throtl low and lay initialization
Date: Thu, 9 May 2024 20:11:05 +0800 [thread overview]
Message-ID: <20240509121107.3195568-1-yukuai1@huaweicloud.com> (raw)
From: Yu Kuai <yukuai3@huawei.com>
Tested with the new blktests:
https://lore.kernel.org/all/20240420084505.3624763-1-yukuai1@huaweicloud.com/
Changes from RFC:
- remove patches to support build blk-throtl as module;
- add ack tag for patch 1, also rebase on the top of for-6.10/block;
- some small changes for patch 2;
Yu Kuai (2):
blk-throttle: remove CONFIG_BLK_DEV_THROTTLING_LOW
blk-throttle: delay initialization until configuration
Documentation/ABI/stable/sysfs-block | 12 -
arch/loongarch/configs/loongson3_defconfig | 1 -
block/Kconfig | 11 -
block/bio.c | 1 -
block/blk-cgroup.c | 6 -
block/blk-stat.c | 3 -
block/blk-sysfs.c | 8 -
block/blk-throttle.c | 996 +++------------------
block/blk-throttle.h | 46 +-
block/blk.h | 11 -
10 files changed, 127 insertions(+), 968 deletions(-)
--
2.39.2
next reply other threads:[~2024-05-09 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 12:11 Yu Kuai [this message]
2024-05-09 12:11 ` [PATCH for-6.10/block 1/2] blk-throttle: remove CONFIG_BLK_DEV_THROTTLING_LOW Yu Kuai
2024-05-09 12:11 ` [PATCH for-6.10/block 2/2] blk-throttle: delay initialization until configuration Yu Kuai
2024-05-09 15:45 ` [PATCH for-6.10/block 0/2] blk-throtl: delete throtl low and lay initialization Jens Axboe
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=20240509121107.3195568-1-yukuai1@huaweicloud.com \
--to=yukuai1@huaweicloud.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=chenhuacai@kernel.org \
--cc=jhs@mojatatu.com \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=raven@themaw.net \
--cc=svenjoac@gmx.de \
--cc=tj@kernel.org \
--cc=twoerner@gmail.com \
--cc=victor@mojatatu.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.com \
--cc=zhaotianrui@loongson.cn \
/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).