From: Jan Kara <jack@suse.cz>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Hou Tao <houtao@huaweicloud.com>, Jan Kara <jack@suse.cz>,
linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
cgroups@vger.kernel.org, Tejun Heo <tj@kernel.org>,
Zefan Li <lizefan.x@bytedance.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
houtao1@huawei.com
Subject: Re: [PATCH] blk-ioprio: Introduce promote-to-rt policy
Date: Tue, 14 Feb 2023 09:52:36 +0100 [thread overview]
Message-ID: <20230214085236.vamd2yuflnyljyid@quack3> (raw)
In-Reply-To: <0290f608-6ddf-ecb7-4c05-55b0f7dbfbea@acm.org>
On Mon 13-02-23 09:10:26, Bart Van Assche wrote:
> On 2/13/23 04:51, Hou Tao wrote:
> > Should I keep "none-to-rt" and make it work just like "promote-to-rt" or should
> > I just remove "none-to-rt" and add "promote-to-rt" ? I think the latter will be
> > more appropriate.
>
> Removing none-to-rt would break existing systems that use this policy. I
> prefer the former solution.
Agreed. I also think that keeping none-to-rt as an alias for promote-to-rt
allows for a smoother transition. However I'm all for documenting that
none-to-rt is deprecated and works as promote-to-rt.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2023-02-14 8:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 4:52 [PATCH] blk-ioprio: Introduce promote-to-rt policy Hou Tao
2023-02-01 9:07 ` Bagas Sanjaya
2023-02-02 10:50 ` Hou Tao
2023-02-01 17:33 ` Bart Van Assche
2023-02-02 11:09 ` Hou Tao
2023-02-02 18:05 ` Bart Van Assche
2023-02-03 1:48 ` Hou Tao
2023-02-03 19:45 ` Bart Van Assche
2023-02-05 7:04 ` Hou Tao
2023-02-08 13:43 ` Jan Kara
2023-02-08 17:53 ` Bart Van Assche
2023-02-09 8:56 ` Jan Kara
2023-02-09 19:09 ` Bart Van Assche
2023-02-10 10:12 ` Jan Kara
2023-02-13 12:51 ` Hou Tao
2023-02-13 17:10 ` Bart Van Assche
2023-02-14 8:52 ` Jan Kara [this message]
2023-02-03 19:51 ` Bart Van Assche
2023-02-05 7:17 ` Hou Tao
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=20230214085236.vamd2yuflnyljyid@quack3 \
--to=jack@suse.cz \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=hannes@cmpxchg.org \
--cc=houtao1@huawei.com \
--cc=houtao@huaweicloud.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--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;
as well as URLs for NNTP newsgroup(s).