From: "Wang Jianchao (Kuaishou)" <jianchao.wan9@gmail.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: hch@infradead.org, Josef Bacik <jbacik@fb.com>,
Tejun Heo <tj@kernel.org>, Bart Van Assche <bvanassche@acm.org>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC V2 0/6] blk: make blk-rq-qos policies pluggable and modular
Date: Tue, 15 Feb 2022 20:36:59 +0800 [thread overview]
Message-ID: <20220215123705.58968-1-jianchao.wan9@gmail.com> (raw)
Hi Jens
blk-rq-qos is a standalone framework out of io-sched and can be used to
control or observe the IO progress in block-layer with hooks. blk-rq-qos
is a great design but right now, it is totally fixed and built-in and shut
out peoples who want to use it with external module.
This patchset attempts to make blk-rq-qos framework pluggable and modular.
Then we can update the blk-rq-qos policy module w/o stopping the IO workload.
And it is more convenient to introduce new policy on old machines w/o udgrade
kernel. And we can close all of the blk-rq-qos policy if we needn't any of
them. At the moment, the request_queue.rqos list is empty, we needn't to
waste cpu cyles on them.
Changes since v1:
- Just make iocost and iolatency pluggable, then we needn't to export
those interfaces
- Remove the iostat rqos policy
- Rename module of blk-ioprio to io-prio to avoid rename ioprio.c file
WangJianchao(6):
blk: make blk-rq-qos support pluggable and modular
blk-wbt: make wbt pluggable
blk-iolatency: make iolatency pluggable
blk-iocost: make iocost pluggable
blk-ioprio: make ioprio pluggable and modular
blk: remove unused interfaces of blk-rq-qos
block/Kconfig | 2 +-
block/Makefile | 3 +-
block/blk-cgroup.c | 11 ---
block/blk-core.c | 2 +
block/blk-iocost.c | 59 ++++++++------
block/blk-iolatency.c | 33 ++++++--
block/blk-ioprio.c | 50 +++++++-----
block/blk-ioprio.h | 19 -----
block/blk-mq-debugfs.c | 18 +----
block/blk-rq-qos.c | 312 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
block/blk-rq-qos.h | 104 +++++++++++--------------
block/blk-sysfs.c | 9 +--
block/blk-wbt.c | 36 +++++++--
block/blk-wbt.h | 8 +-
block/blk.h | 6 --
block/elevator.c | 3 +
block/genhd.c | 2 -
include/linux/blkdev.h | 4 +
18 files changed, 501 insertions(+), 180 deletions(-)
next reply other threads:[~2022-02-15 12:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 12:36 Wang Jianchao (Kuaishou) [this message]
2022-02-15 12:37 ` [RFC V2 1/6] blk: make blk-rq-qos support pluggable and modular policy Wang Jianchao (Kuaishou)
2022-02-15 21:23 ` Bart Van Assche
2022-02-16 2:11 ` Wang Jianchao
2022-02-15 12:37 ` [RFC V2 2/6] blk-wbt: make wbt pluggable Wang Jianchao (Kuaishou)
2022-02-15 12:37 ` [RFC V2 3/6] blk-iolatency: make iolatency pluggable Wang Jianchao (Kuaishou)
2022-02-15 12:37 ` [RFC V2 4/6] blk-iocost: make iocost pluggable Wang Jianchao (Kuaishou)
2022-02-15 12:37 ` [RFC V2 5/6] blk-ioprio: make ioprio pluggable and modular Wang Jianchao (Kuaishou)
2022-02-15 21:26 ` Bart Van Assche
2022-02-16 2:09 ` Wang Jianchao
2022-02-16 18:01 ` Bart Van Assche
2022-02-17 2:56 ` Wang Jianchao
2022-02-15 12:37 ` [RFC V2 6/6] blk: remove unused interfaces of blk-rq-qos Wang Jianchao (Kuaishou)
2022-02-15 13:01 ` [RFC V2 0/6] blk: make blk-rq-qos policies pluggable and modular Chaitanya Kulkarni
2022-02-16 1:43 ` Wang Jianchao
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=20220215123705.58968-1-jianchao.wan9@gmail.com \
--to=jianchao.wan9@gmail.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hch@infradead.org \
--cc=jbacik@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®