From: Suwan Kim <suwan.kim027@gmail.com>
To: Max Gurtovoy <mgurtovoy@nvidia.com>
Cc: mst@redhat.com, jasowang@redhat.com, pbonzini@redhat.com,
stefanha@redhat.com, virtualization@lists.linux-foundation.org,
linux-block@vger.kernel.org, suwan027.kim@gmail.com
Subject: Re: [PATCH] virtio-blk: support polling I/O
Date: Mon, 14 Mar 2022 18:55:48 +0900 [thread overview]
Message-ID: <Yi8RJHO4XDDKYHAF@localhost.localdomain> (raw)
In-Reply-To: <c851906c-c619-4e87-3272-9c41ac256052@nvidia.com>
On Sun, Mar 13, 2022 at 12:42:58PM +0200, Max Gurtovoy wrote:
>
> On 3/11/2022 5:28 PM, Suwan Kim wrote:
> > This patch supports polling I/O via virtio-blk driver. Polling
> > feature is enabled based on "VIRTIO_BLK_F_MQ" feature and the number
> > of polling queues can be set by QEMU virtio-blk-pci property
> > "num-poll-queues=N". This patch improves the polling I/O throughput
> > and latency.
> >
> > The virtio-blk driver doesn't not have a poll function and a poll
> > queue and it has been operating in interrupt driven method even if
> > the polling function is called in the upper layer.
> >
> > virtio-blk polling is implemented upon 'batched completion' of block
> > layer. virtblk_poll() queues completed request to io_comp_batch->req_list
> > and later, virtblk_complete_batch() calls unmap function and ends
> > the requests in batch.
>
> Maybe we can do the batch in separate commit ?
>
> For implementing batch in the right way you need to implement .queue_rqs
> call back.
>
> See NVMe PCI driver implementation.
>
> If we're here, I would really like to see an implementation of
> blk_mq_ops.timeout callback in virtio-blk.
>
> I think it will take this driver to the next level.
Thanks for the feedback. I will implement .queue_rqs for virtio-blk
and make a seperate commit. Later, I will try to implement
blk_mq_ops.timeout as you mentioned.
I will send the patch series soon as below.
[1] support .queue_rqs for batch submission
[2] support polling I/O
Regards,
Suwan Kim
next prev parent reply other threads:[~2022-03-14 9:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 15:28 [PATCH] virtio-blk: support polling I/O Suwan Kim
2022-03-11 15:38 ` Michael S. Tsirkin
2022-03-11 16:07 ` Suwan Kim
2022-03-11 16:18 ` Michael S. Tsirkin
2022-03-11 16:38 ` Suwan Kim
2022-03-13 10:37 ` Max Gurtovoy
2022-03-14 9:43 ` Suwan Kim
2022-03-14 10:25 ` Max Gurtovoy
2022-03-14 11:15 ` Michael S. Tsirkin
2022-03-14 13:22 ` Suwan Kim
2022-03-14 15:12 ` Michael S. Tsirkin
2022-03-14 13:26 ` Max Gurtovoy
2022-03-14 15:15 ` Michael S. Tsirkin
2022-03-14 16:33 ` Max Gurtovoy
2022-03-14 22:22 ` Michael S. Tsirkin
2022-03-13 10:42 ` Max Gurtovoy
2022-03-14 9:55 ` Suwan Kim [this message]
2022-03-14 10:32 ` Max Gurtovoy
2022-03-14 6:14 ` Jason Wang
2022-03-14 12:33 ` Suwan Kim
2022-03-14 14:48 ` Stefan Hajnoczi
[not found] ` <CACGkMEujXYNE-88=m9ohjbeAj2F7CqEUes8gOUmasTNtwn2bUA@mail.gmail.com>
2022-03-15 14:43 ` Suwan Kim
2022-03-15 14:53 ` Michael S. Tsirkin
2022-03-16 2:02 ` Jason Wang
2022-03-16 11:25 ` Max Gurtovoy
2022-03-16 13:32 ` Suwan Kim
2022-03-16 15:32 ` Suwan Kim
2022-03-16 15:36 ` Max Gurtovoy
2022-03-16 16:00 ` Stefan Hajnoczi
2022-03-17 2:20 ` Jason Wang
2022-03-17 15:03 ` Suwan Kim
2022-03-14 15:19 ` Stefan Hajnoczi
2022-03-15 13:55 ` Suwan Kim
2022-03-16 12:20 ` Stefan Hajnoczi
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=Yi8RJHO4XDDKYHAF@localhost.localdomain \
--to=suwan.kim027@gmail.com \
--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=suwan027.kim@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;
as well as URLs for NNTP newsgroup(s).