From: Parav Pandit <parav@nvidia.com>
To: <mst@redhat.com>, <virtio-dev@lists.oasis-open.org>, <cohuck@redhat.com>
Cc: <sgarzare@redhat.com>, <pasic@linux.ibm.com>,
<david.edmondson@oracle.com>,
<virtio-comment@lists.oasis-open.org>, <shahafs@nvidia.com>,
Parav Pandit <parav@nvidia.com>
Subject: [virtio-dev] [PATCH v17 01/11] content: Add vq index text
Date: Fri, 5 May 2023 04:46:04 +0300 [thread overview]
Message-ID: <20230505014614.571520-2-parav@nvidia.com> (raw)
In-Reply-To: <20230505014614.571520-1-parav@nvidia.com>
Introduce vq index and its range so that subsequent patches can refer
to it.
Fixes: https://github.com/oasis-tcs/virtio-spec/issues/163
Reviewed-by: David Edmondson <david.edmondson@oracle.com>
Reviewed-by: Halil Pasic <pasic@linux.ibm.com>
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
changelog:
v15->v16:
- rewrote for better reading
v12->v13:
- avoid virtqueue -> vq abbreviation
- removed Cornelia's reviewed-by due to vq abbreviation change
v11->v12:
- renamed 'number' to 'index'
v9->v10:
- added braces around vq number wording
- added vqn as another term for vq number
v8->v9:
- added inclusive when describing the vq number range
- skipped comment to put virtqueue number wording first because we
prefer to use shorter vq number as much as possible
v5->v6:
- moved description close to introduction, it was in middle of
queue data transfer description
v2->v3:
- new patch
---
content.tex | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/content.tex b/content.tex
index cff548a..9b694f2 100644
--- a/content.tex
+++ b/content.tex
@@ -298,6 +298,10 @@ \section{Virtqueues}\label{sec:Basic Facilities of a Virtio Device / Virtqueues}
virtqueues\footnote{For example, the simplest network device has one virtqueue for
transmit and one for receive.}.
+A virtio device can have maximum of 65536 virtqueues. Each virtqueue is
+identified by a virtqueue index. A virtqueue index has a value in the
+range of 0 to 65535.
+
Driver makes requests available to device by adding
an available buffer to the queue, i.e., adding a buffer
describing the request to a virtqueue, and optionally triggering
--
2.26.2
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-05-05 1:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 1:46 [virtio-dev] [PATCH v17 00/11] Rename queue number to queue index Parav Pandit
2023-05-05 1:46 ` Parav Pandit [this message]
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 02/11] content.tex Replace virtqueue number with index Parav Pandit
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 03/11] content: Rename confusing queue_notify_data and vqn names Parav Pandit
2023-05-05 8:04 ` [virtio-dev] " David Edmondson
2023-05-15 9:42 ` Cornelia Huck
2023-05-15 15:10 ` [virtio-dev] " Parav Pandit
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 04/11] transport-pci: Avoid first vq index reference Parav Pandit
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 05/11] transport-mmio: Rename QueueNum register Parav Pandit
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 06/11] transport-mmio: Avoid referring to zero based index Parav Pandit
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 07/11] transport-ccw: Rename queue depth/size to other transports Parav Pandit
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 08/11] transport-ccw: Refer to the vq by its index Parav Pandit
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 09/11] virtio-net: Avoid duplicate receive queue example Parav Pandit
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 10/11] virtio-net: Describe RSS using rss rq id Parav Pandit
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 11/11] virtio-net: Update vqn to vq_index for cvq cmds Parav Pandit
2023-05-11 16:18 ` [virtio-dev] RE: [PATCH v17 00/11] Rename queue number to queue index Parav Pandit
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=20230505014614.571520-2-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=david.edmondson@oracle.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=sgarzare@redhat.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).