[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <ABA117F8-58AA-40EC-B3DA-4AB000A72BAD@smartx.com>
Date: Thu, 7 Dec 2023 14:32:43 +0800
From: Li Feng <fengli@...rtx.com>
To: Jason Wang <jasowang@...hat.com>
Cc: Jens Axboe <axboe@...nel.dk>,
"Michael S. Tsirkin" <mst@...hat.com>,
Paolo Bonzini <pbonzini@...hat.com>,
Stefan Hajnoczi <stefanha@...hat.com>,
Xuan Zhuo <xuanzhuo@...ux.alibaba.com>,
"open list:BLOCK LAYER" <linux-block@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
"open list:VIRTIO BLOCK AND SCSI DRIVERS"
<virtualization@...ts.linux.dev>
Subject: Re: [PATCH] virtio_blk: set the default scheduler to none
> On Dec 7, 2023, at 14:02, Jason Wang <jasowang@...hat.com> wrote:
>
> On Thu, Dec 7, 2023 at 12:33 PM Li Feng <fengli@...rtx.com> wrote:
>>
>> virtio-blk is generally used in cloud computing scenarios, where the
>> performance of virtual disks is very important. The mq-deadline scheduler
>> has a big performance drop compared to none with single queue.
>
> At least you can choose the scheduler based on if mq is supported or not?
>
> Thanks
>
The "none" scheduler has better performance regardless of whether it is
a single queue or multiple queues. Why not set the single queue scheduler
to none by default?
Thanks.
Powered by blists - more mailing lists