From: Christoph Hellwig <hch@infradead.org>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: axboe@kernel.dk, tj@kernel.org, josef@toxicpanda.com,
gregkh@linuxfoundation.org, lizefan.x@bytedance.com,
hannes@cmpxchg.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
yukuai3@huawei.com, yi.zhang@huawei.com, yangerkun@huawei.com
Subject: Re: [PATCH RFC -next 0/7] blk-iocost: support to build iocost as kernel module
Date: Thu, 13 Jun 2024 22:26:16 -0700 [thread overview]
Message-ID: <ZmvUeNI4jF3f_seK@infradead.org> (raw)
In-Reply-To: <20240613014937.1326020-1-yukuai1@huaweicloud.com>
This cover letter is a little, erm, sparse.
Please explain why you want iocost as a module. This adds a whole
lot of infrastructure for no obvious reason.
prev parent reply other threads:[~2024-06-14 5:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 1:49 [PATCH RFC -next 0/7] blk-iocost: support to build iocost as kernel module Yu Kuai
2024-06-13 1:49 ` [PATCH RFC -next 1/7] kernfs: export pr_cont_kernfs_path() Yu Kuai
2024-06-13 5:55 ` Greg KH
2024-06-13 6:55 ` Yu Kuai
2024-06-13 1:49 ` [PATCH RFC -next 2/7] cgroup: export cgroup_parse_float Yu Kuai
2024-06-13 1:49 ` [PATCH RFC -next 3/7] block: export some API Yu Kuai
2024-06-13 1:49 ` [PATCH RFC -next 4/7] blk-iocost: factor out helpers to handle params from ioc_qos_write() Yu Kuai
2024-06-13 1:49 ` [PATCH RFC -next 5/7] blk-iocost: parse params before initializing iocost Yu Kuai
2024-06-13 1:49 ` [PATCH RFC -next 6/7] blk-iocost: support to free iocost Yu Kuai
2024-06-13 1:49 ` [PATCH RFC -next 7/7] blk-iocost: support to build iocost as kernel module Yu Kuai
2024-06-13 5:54 ` Greg KH
2024-06-13 5:54 ` [PATCH RFC -next 0/7] " Greg KH
2024-06-13 6:53 ` Yu Kuai
2024-06-13 16:15 ` Bart Van Assche
2024-06-14 1:07 ` Yu Kuai
2024-06-14 5:26 ` Christoph Hellwig [this message]
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=ZmvUeNI4jF3f_seK@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=tj@kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.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).