From: "Michael S. Tsirkin" <mst@redhat.com>
To: Zhu Lingshan <lingshan.zhu@intel.com>
Cc: jasowang@redhat.com, cohuck@redhat.com, sgarzare@redhat.com,
stefanha@redhat.com, nrupal.jani@intel.com,
Piotr.Uminski@intel.com, virtio-comment@lists.oasis-open.org
Subject: Re: [PATCH V2 5/5] Add transport vq number for virtio blk and net
Date: Mon, 1 Aug 2022 16:54:21 -0400 [thread overview]
Message-ID: <20220801165342-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220801093216.362119-6-lingshan.zhu@intel.com>
On Mon, Aug 01, 2022 at 05:32:16PM +0800, Zhu Lingshan wrote:
> This commit add the queue number of the transport virtqueue
> for virtio_blk and virtio_net
>
> Signed-off-by: Jason Wang <jasowang@redhat.com>
> Signed-off-by: Zhu Lingshan <lingshan.zhu@intel.com>
I think I prefer a transport register for this.
Otherwise, you most document that other devices must not offer
the feature bit.
> ---
> content.tex | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/content.tex b/content.tex
> index 2d4816d..2536d2a 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -3801,6 +3801,7 @@ \subsection{Virtqueues}\label{sec:Device Types / Network Device / Virtqueues}
> \item[2(N-1)] receiveqN
> \item[2(N-1)+1] transmitqN
> \item[2N] controlq
> +\item[2N+1] transportq
> \end{description}
>
> N=1 if neither VIRTIO_NET_F_MQ nor VIRTIO_NET_F_RSS are negotiated, otherwise N is set by
> @@ -3808,6 +3809,8 @@ \subsection{Virtqueues}\label{sec:Device Types / Network Device / Virtqueues}
>
> controlq only exists if VIRTIO_NET_F_CTRL_VQ set.
>
> + transportq only exists if VIRTIO_F_TRANSPT_VQ set
> +
> \subsection{Feature bits}\label{sec:Device Types / Network Device / Feature bits}
>
> \begin{description}
> @@ -5387,11 +5390,14 @@ \subsection{Virtqueues}\label{sec:Device Types / Block Device / Virtqueues}
> \item[0] requestq1
> \item[\ldots]
> \item[N-1] requestqN
> +\item[N] transportq
> \end{description}
>
> N=1 if VIRTIO_BLK_F_MQ is not negotiated, otherwise N is set by
> \field{num_queues}.
>
> + transportq only exists if VIRTIO_F_TRANSPT_VQ set.
> +
> \subsection{Feature bits}\label{sec:Device Types / Block Device / Feature bits}
>
> \begin{description}
> --
> 2.35.3
next prev parent reply other threads:[~2022-08-01 20:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 9:32 [PATCH V2 0/5] Introduce virtio transport virtqueue Zhu Lingshan
2022-08-01 9:32 ` [PATCH V2 1/5] Introduce virito " Zhu Lingshan
2022-08-01 20:25 ` Michael S. Tsirkin
2022-08-02 2:54 ` Zhu, Lingshan
2022-08-01 9:32 ` [PATCH V2 2/5] Introduce feature bit VIRTIO_F_TRANSPT_VQ_MDEV Zhu Lingshan
2022-08-01 20:27 ` [virtio-comment] " Michael S. Tsirkin
2022-08-02 3:17 ` Zhu, Lingshan
2022-08-02 6:32 ` Zhu, Lingshan
2022-08-02 6:52 ` Michael S. Tsirkin
2022-08-02 11:54 ` Zhu, Lingshan
2022-08-02 12:55 ` Michael S. Tsirkin
2022-08-02 13:15 ` Zhu, Lingshan
2022-08-02 13:20 ` Michael S. Tsirkin
2022-08-02 13:32 ` Zhu, Lingshan
2022-08-02 13:37 ` Zhu, Lingshan
2022-08-01 9:32 ` [PATCH V2 3/5] Introduce the commands set of the transport vq Zhu Lingshan
2022-08-01 20:53 ` Michael S. Tsirkin
2022-08-02 13:07 ` [virtio-comment] " Zhu, Lingshan
2022-08-01 9:32 ` [PATCH V2 4/5] Describe the process to present a managed device Zhu Lingshan
2022-08-01 9:32 ` [PATCH V2 5/5] Add transport vq number for virtio blk and net Zhu Lingshan
2022-08-01 20:54 ` Michael S. Tsirkin [this message]
2022-08-01 9:48 ` [PATCH V2 0/5] Introduce virtio transport virtqueue Michael S. Tsirkin
2022-08-01 20:56 ` Michael S. Tsirkin
2022-08-02 13:18 ` [virtio-comment] " Zhu, Lingshan
2022-08-02 13:21 ` Zhu, Lingshan
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=20220801165342-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=Piotr.Uminski@intel.com \
--cc=cohuck@redhat.com \
--cc=jasowang@redhat.com \
--cc=lingshan.zhu@intel.com \
--cc=nrupal.jani@intel.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtio-comment@lists.oasis-open.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