From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Suwan Kim <suwan.kim027@gmail.com>
Cc: "virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"mst@redhat.com" <mst@redhat.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"stefanha@redhat.com" <stefanha@redhat.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"elliott@hpe.com" <elliott@hpe.com>,
"dongli.zhang@oracle.com" <dongli.zhang@oracle.com>,
"hch@infradead.org" <hch@infradead.org>,
Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: Re: [PATCH v6 0/2] virtio-blk: support polling I/O and mq_ops->queue_rqs()
Date: Mon, 11 Apr 2022 23:47:34 +0000 [thread overview]
Message-ID: <86a7c623-7494-ece3-d607-63a497eb8068@nvidia.com> (raw)
In-Reply-To: <YlBOgKV/y/9bCWD4@localhost.localdomain>
>
> Hi Chaitanya,
>
> Sure. I will do.
> Do I need to add a new test script about vdN device IO polling
> to blktests/tests/block/?
>
That will create confusion as block category testcases are different
than virtio-blk. So you need to create a new category virtio-blk and
add testcases to that one.
-ck
> Regards,
> Suwan Kim
>
next prev parent reply other threads:[~2022-04-11 23:47 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
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 [this message]
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=86a7c623-7494-ece3-d607-63a497eb8068@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=dongli.zhang@oracle.com \
--cc=elliott@hpe.com \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.