From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Suwan Kim <suwan.kim027@gmail.com>,
"mst@redhat.com" <mst@redhat.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"stefanha@redhat.com" <stefanha@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
Max Gurtovoy <mgurtovoy@nvidia.com>,
"dongli.zhang@oracle.com" <dongli.zhang@oracle.com>,
"hch@infradead.org" <hch@infradead.org>,
"elliott@hpe.com" <elliott@hpe.com>
Cc: "virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v6 2/2] virtio-blk: support mq_ops->queue_rqs()
Date: Thu, 7 Apr 2022 19:33:05 +0000 [thread overview]
Message-ID: <3b66fe79-74c2-d3ef-ef27-f4e1e3efb4aa@nvidia.com> (raw)
In-Reply-To: <20220406153207.163134-3-suwan.kim027@gmail.com>
On 4/6/22 08:32, Suwan Kim wrote:
> This patch supports mq_ops->queue_rqs() hook. It has an advantage of
> batch submission to virtio-blk driver. It also helps polling I/O because
> polling uses batched completion of block layer. Batch submission in
> queue_rqs() can boost polling performance.
>
> In queue_rqs(), it iterates plug->mq_list, collects requests that
> belong to same HW queue until it encounters a request from other
> HW queue or sees the end of the list.
> Then, virtio-blk adds requests into virtqueue and kicks virtqueue
> to submit requests.
>
> If there is an error, it inserts error request to requeue_list and
> passes it to ordinary block layer path.
>
> For verification, I did fio test.
> (io_uring, randread, direct=1, bs=4K, iodepth=64 numjobs=N)
> I set 4 vcpu and 2 virtio-blk queues for VM and run fio test 5 times.
> It shows about 2% improvement.
>
> | numjobs=2 | numjobs=4
> -----------------------------------------------------------
> fio without queue_rqs() | 291K IOPS | 238K IOPS
> -----------------------------------------------------------
> fio with queue_rqs() | 295K IOPS | 243K IOPS
>
> For polling I/O performance, I also did fio test as below.
> (io_uring, hipri, randread, direct=1, bs=512, iodepth=64 numjobs=4)
> I set 4 vcpu and 2 poll queues for VM.
> It shows about 2% improvement in polling I/O.
>
> | IOPS | avg latency
> -----------------------------------------------------------
> fio poll without queue_rqs() | 424K | 613.05 usec
> -----------------------------------------------------------
> fio poll with queue_rqs() | 435K | 601.01 usec
>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Suwan Kim <suwan.kim027@gmail.com>
> ---
Looks good.
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
next prev parent reply other threads:[~2022-04-07 20:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 15:32 [PATCH v6 0/2] virtio-blk: support polling I/O and mq_ops->queue_rqs() Suwan Kim
2022-04-06 15:32 ` [PATCH v6 1/2] virtio-blk: support polling I/O Suwan Kim
2022-04-07 19:32 ` Chaitanya Kulkarni
2022-04-06 15:32 ` [PATCH v6 2/2] virtio-blk: support mq_ops->queue_rqs() Suwan Kim
2022-04-07 19:33 ` Chaitanya Kulkarni [this message]
2022-04-07 19:36 ` [PATCH v6 0/2] virtio-blk: support polling I/O and mq_ops->queue_rqs() Chaitanya Kulkarni
2022-04-08 15:02 ` Suwan Kim
2022-04-11 23:47 ` Chaitanya Kulkarni
2022-05-18 13:20 ` Suwan Kim
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=3b66fe79-74c2-d3ef-ef27-f4e1e3efb4aa@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=dongli.zhang@oracle.com \
--cc=elliott@hpe.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=jasowang@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=mgurtovoy@nvidia.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=stefanha@redhat.com \
--cc=suwan.kim027@gmail.com \
--cc=virtualization@lists.linux-foundation.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