From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Li Jinlin <lijinlin3@huawei.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linfeilong@huawei.com" <linfeilong@huawei.com>
Subject: Re: [PATCH] block/blk-rq-qos: delete useless enmu RQ_QOS_IOPRIO
Date: Sat, 17 Sep 2022 16:30:42 +0000 [thread overview]
Message-ID: <fe9863c8-af50-32f2-9b3a-ee631a50a874@nvidia.com> (raw)
In-Reply-To: <20220916023241.32926-1-lijinlin3@huawei.com>
On 9/15/2022 7:32 PM, Li Jinlin wrote:
> Since blk-ioprio handing was converted from a rqos policy to a direct call,
> RQ_QOS_IOPRIO is not used anymore, just delete it.
>
> Signed-off-by: Li Jinlin <lijinlin3@huawei.com>
>
Perhaps mention about when it was removed.
Either way,
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
next prev parent reply other threads:[~2022-09-17 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 2:32 [PATCH] block/blk-rq-qos: delete useless enmu RQ_QOS_IOPRIO Li Jinlin
2022-09-16 14:12 ` Bart Van Assche
2022-09-16 21:58 ` Jan Kara
2022-09-19 16:38 ` Bart Van Assche
2022-09-17 16:30 ` Chaitanya Kulkarni [this message]
2022-09-22 1:51 ` 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=fe9863c8-af50-32f2-9b3a-ee631a50a874@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=lijinlin3@huawei.com \
--cc=linfeilong@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).