From: Bart Van Assche <bvanassche@acm.org>
To: Yu Kuai <yukuai1@huaweicloud.com>, Jens Axboe <axboe@kernel.dk>,
jack@suse.cz, tj@kernel.org, josef@toxicpanda.com,
paolo.valente@unimore.it, mauro.andreolini@unimore.it,
avanzini.arianna@gmail.com
Cc: cgroups@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com,
yangerkun@huawei.com, "yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH for-6.12 0/4] block, bfq: fix corner cases related to bfqq merging
Date: Tue, 3 Sep 2024 19:28:42 -0700 [thread overview]
Message-ID: <b5b0e655-fb17-4967-9104-4386710ee8db@acm.org> (raw)
In-Reply-To: <c2a6d239-aa96-f767-9767-9e9ea929b014@huaweicloud.com>
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.
Thanks,
Bart.
next prev parent reply other threads:[~2024-09-04 2:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 13:03 [PATCH for-6.12 0/4] block, bfq: fix corner cases related to bfqq merging Yu Kuai
2024-09-02 13:03 ` [PATCH for-6.12 1/4] block, bfq: fix possible UAF for bfqq->bic with merge chain Yu Kuai
2024-09-04 11:51 ` Jan Kara
2024-09-02 13:03 ` [PATCH for-6.12 2/4] block, bfq: choose the last bfqq from merge chain in bfq_setup_cooperator() Yu Kuai
2024-09-04 12:17 ` Jan Kara
2024-09-02 13:03 ` [PATCH for-6.12 3/4] block, bfq: don't break merge chain in bfq_split_bfqq() Yu Kuai
2024-09-04 12:20 ` Jan Kara
2024-09-02 13:03 ` [PATCH for-6.12 4/4] block, bfq: use bfq_reassign_last_bfqq() in bfq_bfqq_move() Yu Kuai
2024-09-04 12:22 ` Jan Kara
2024-09-03 15:51 ` [PATCH for-6.12 0/4] block, bfq: fix corner cases related to bfqq merging Jens Axboe
2024-09-04 1:32 ` Yu Kuai
2024-09-04 2:28 ` Bart Van Assche [this message]
2024-09-04 2:45 ` Yu Kuai
2024-09-04 13:55 ` Jens Axboe
2024-09-04 17:17 ` Bart Van Assche
2024-09-05 1:48 ` Yu Kuai
2024-09-04 4:38 ` Ming Lei
2024-09-04 12:29 ` Jan Kara
2024-09-04 13:49 ` Jens Axboe
2024-09-04 13:53 ` Jens Axboe
2024-09-03 15:56 ` 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=b5b0e655-fb17-4967-9104-4386710ee8db@acm.org \
--to=bvanassche@acm.org \
--cc=avanzini.arianna@gmail.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=jack@suse.cz \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mauro.andreolini@unimore.it \
--cc=paolo.valente@unimore.it \
--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