virtio-comment.lists.oasis-open.org archive mirror
 help / color / mirror / Atom feed
From: Parav Pandit <parav@nvidia.com>
To: <mst@redhat.com>, <virtio-dev@lists.oasis-open.org>,
	<pasic@linux.ibm.com>, <cohuck@redhat.com>
Cc: <virtio-comment@lists.oasis-open.org>, <shahafs@nvidia.com>,
	Parav Pandit <parav@nvidia.com>
Subject: [virtio-comment] [PATCH v4 1/8] content: Add vq number text
Date: Wed, 22 Mar 2023 23:52:36 +0200	[thread overview]
Message-ID: <20230322215243.249524-2-parav@nvidia.com> (raw)
In-Reply-To: <20230322215243.249524-1-parav@nvidia.com>

Introduce vq number and its range so that subsequent patches can refer
to it.

Fixes: https://github.com/oasis-tcs/virtio-spec/issues/163
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
changelog:
v2->v3:
- new patch
---
 content.tex | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/content.tex b/content.tex
index cff548a..1ab7794 100644
--- a/content.tex
+++ b/content.tex
@@ -321,6 +321,9 @@ \section{Virtqueues}\label{sec:Basic Facilities of a Virtio Device / Virtqueues}
 VIRTIO_F_IN_ORDER feature. If negotiated, this knowledge
 might allow optimizations or simplify driver and/or device code.
 
+Each virtqueue is identified as vq number or also referred
+to as a virtqueue number; vq number range is from 0 to 65535.
+
 Each virtqueue can consist of up to 3 parts:
 \begin{itemize}
 \item Descriptor Area - used for describing buffers
-- 
2.26.2


This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/


  reply	other threads:[~2023-03-22 21:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22 21:52 [virtio-comment] [PATCH v4 0/8] Rename queue index to queue number Parav Pandit
2023-03-22 21:52 ` Parav Pandit [this message]
2023-03-22 21:52 ` [virtio-comment] [PATCH v4 2/8] transport-pci: Refer to the vq by its number Parav Pandit
2023-03-27 22:48   ` Max Gurtovoy
2023-03-27 23:19     ` Parav Pandit
2023-03-22 21:52 ` [virtio-comment] [PATCH v4 3/8] transport-mmio: Rename QueueNum register Parav Pandit
2023-03-22 21:52 ` [virtio-comment] [PATCH v4 4/8] transport-mmio: Refer to the vq by its number Parav Pandit
2023-03-22 21:52 ` [virtio-comment] [PATCH v4 5/8] transport-ccw: Rename queue depth/size to other transports Parav Pandit
2023-03-22 21:52 ` [virtio-comment] [PATCH v4 6/8] transport-ccw: Refer to the vq by its number Parav Pandit
2023-03-22 21:52 ` [virtio-comment] [PATCH v4 7/8] virtio-net: Avoid duplicate receive queue example Parav Pandit
2023-03-22 21:52 ` [virtio-comment] [PATCH v4 8/8] virtio-net: Describe RSS using receive queue handle Parav Pandit
2023-03-22 23:03   ` [virtio-comment] " Michael S. Tsirkin
2023-03-22 23:47     ` [virtio-comment] " Parav Pandit
2023-03-22 23:04 ` [virtio-comment] Re: [PATCH v4 0/8] Rename queue index to queue number Michael S. Tsirkin

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=20230322215243.249524-2-parav@nvidia.com \
    --to=parav@nvidia.com \
    --cc=cohuck@redhat.com \
    --cc=mst@redhat.com \
    --cc=pasic@linux.ibm.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 NNTP newsgroup(s).