From: Suwan Kim <suwan.kim027@gmail.com>
To: Dongli Zhang <dongli.zhang@oracle.com>
Cc: mst@redhat.com, jasowang@redhat.com, stefanha@redhat.com,
pbonzini@redhat.com, mgurtovoy@nvidia.com,
virtualization@lists.linux-foundation.org,
linux-block@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v3 1/2] virtio-blk: support polling I/O
Date: Sat, 26 Mar 2022 20:53:21 +0900 [thread overview]
Message-ID: <Yj7+sasrVSWnVcAf@localhost.localdomain> (raw)
In-Reply-To: <50bfac4d-5111-6724-4fca-4499627b909c@oracle.com>
On Thu, Mar 24, 2022 at 10:34:04AM -0700, Dongli Zhang wrote:
> Hi Suwan,
>
> The NVMe prints something like below by nvme_setup_io_queues() to confirm
> if the configuration takes effect.
>
> "[ 0.620458] nvme nvme0: 4/0/0 default/read/poll queues".
>
> How about to print in virtio-blk as well?
Hi Dongli,
Thansk for your feedback. It is good idea.
I will add it in next version.
Regards,
Suwan Kim
next prev parent reply other threads:[~2022-03-26 11:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 14:04 [PATCH v3 0/2] virtio-blk: support polling I/O and mq_ops->queue_rqs() Suwan Kim
2022-03-24 14:04 ` [PATCH v3 1/2] virtio-blk: support polling I/O Suwan Kim
2022-03-24 14:32 ` Michael S. Tsirkin
2022-03-24 14:46 ` Suwan Kim
2022-03-24 17:56 ` Michael S. Tsirkin
2022-03-26 12:00 ` Suwan Kim
2022-03-24 17:34 ` Dongli Zhang
2022-03-26 11:53 ` Suwan Kim [this message]
2022-03-24 17:58 ` Michael S. Tsirkin
2022-03-26 12:44 ` Suwan Kim
2022-03-28 12:53 ` Stefan Hajnoczi
2022-03-28 14:40 ` Suwan Kim
2022-03-24 14:04 ` [PATCH v3 2/2] virtio-blk: support mq_ops->queue_rqs() Suwan Kim
2022-03-28 13:16 ` Stefan Hajnoczi
2022-03-28 15:50 ` Suwan Kim
2022-03-29 8:45 ` Stefan Hajnoczi
2022-03-29 13:48 ` Suwan Kim
2022-03-29 15:01 ` Stefan Hajnoczi
2022-03-29 15:54 ` 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=Yj7+sasrVSWnVcAf@localhost.localdomain \
--to=suwan.kim027@gmail.com \
--cc=dongli.zhang@oracle.com \
--cc=jasowang@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mgurtovoy@nvidia.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=stefanha@redhat.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).