[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <80732d0d-e1a6-8b5e-791d-7c8a8091159a@huaweicloud.com>
Date: Wed, 4 Sep 2024 10:45:22 +0800
From: Yu Kuai <yukuai1@...weicloud.com>
To: Bart Van Assche <bvanassche@....org>, Yu Kuai <yukuai1@...weicloud.com>,
Jens Axboe <axboe@...nel.dk>, jack@...e.cz, tj@...nel.org,
josef@...icpanda.com, paolo.valente@...more.it, mauro.andreolini@...more.it,
avanzini.arianna@...il.com
Cc: cgroups@...r.kernel.org, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, yi.zhang@...wei.com, yangerkun@...wei.com,
"yukuai (C)" <yukuai3@...wei.com>
Subject: Re: [PATCH for-6.12 0/4] block, bfq: fix corner cases related to bfqq
merging
Hi,
在 2024/09/04 10:28, Bart Van Assche 写道:
> On 9/3/24 6:32 PM, Yu Kuai wrote:
>> We do have customers are using bfq in downstream kernels, and we are
>> still running lots of test for bfq.
>
> It may take less time to add any missing functionality to another I/O
> scheduler rather than to keep maintaining BFQ.
>
> If Android device vendors would stop using BFQ, my job would become
> easier.
I'm confused now, I think keep maintaining BFQ won't stop you from
adding new functionality to another scheduler, right? Is this something
that all scheduler have to support?
Thanks,
Kuai
>
> Thanks,
>
> Bart.
> .
>
Powered by blists - more mailing lists