[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230214085236.vamd2yuflnyljyid@quack3>
Date: Tue, 14 Feb 2023 09:52:36 +0100
From: Jan Kara <jack@...e.cz>
To: Bart Van Assche <bvanassche@....org>
Cc: Hou Tao <houtao@...weicloud.com>, Jan Kara <jack@...e.cz>,
linux-block@...r.kernel.org, Jens Axboe <axboe@...nel.dk>,
cgroups@...r.kernel.org, Tejun Heo <tj@...nel.org>,
Zefan Li <lizefan.x@...edance.com>,
Johannes Weiner <hannes@...xchg.org>,
Jonathan Corbet <corbet@....net>, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, houtao1@...wei.com
Subject: Re: [PATCH] blk-ioprio: Introduce promote-to-rt policy
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@...e.com>
SUSE Labs, CR
Powered by blists - more mailing lists