From: David Edmondson <david.edmondson@oracle.com>
To: Parav Pandit <parav@nvidia.com>,
mst@redhat.com, virtio-dev@lists.oasis-open.org,
pasic@linux.ibm.com, cohuck@redhat.com
Cc: sgarzare@redhat.com, virtio-comment@lists.oasis-open.org,
shahafs@nvidia.com, Parav Pandit <parav@nvidia.com>
Subject: [virtio-comment] Re: [virtio-dev] [PATCH v8 1/8] content: Add vq number text
Date: Tue, 28 Mar 2023 14:56:47 +0100 [thread overview]
Message-ID: <m2bkkdc734.fsf@oracle.com> (raw)
In-Reply-To: <20230327235936.414196-2-parav@nvidia.com>
Parav Pandit <parav@nvidia.com> writes:
> 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:
> v5->v6:
> - moved description close to introduction, it was in middle of
> queue data transfer description
> v2->v3:
> - new patch
> ---
> content.tex | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/content.tex b/content.tex
> index cff548a..5171c12 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -298,6 +298,9 @@ \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.}.
>
> +Each virtqueue is identified by a vq number or also referred
> +to as a virtqueue number; vq number range is from 0 to 65535.
> +
It would be nice to use the unabbreviated version first, and we could
also include "vqn", as it's in use during discussions:
Each virtqueue is identified by a virtqueue number, also referred to
as a vq number or vqn. The range of virtqueue numbers is 0 to 65535
inclusive.
> 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
--
The sound of a barking dog on a loop, a plane rises in the crystal blue.
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/
WARNING: multiple messages have this Message-ID (diff)
From: David Edmondson <david.edmondson@oracle.com>
To: Parav Pandit <parav@nvidia.com>,
mst@redhat.com, virtio-dev@lists.oasis-open.org,
pasic@linux.ibm.com, cohuck@redhat.com
Cc: sgarzare@redhat.com, virtio-comment@lists.oasis-open.org,
shahafs@nvidia.com, Parav Pandit <parav@nvidia.com>
Subject: Re: [virtio-dev] [PATCH v8 1/8] content: Add vq number text
Date: Tue, 28 Mar 2023 14:56:47 +0100 [thread overview]
Message-ID: <m2bkkdc734.fsf@oracle.com> (raw)
In-Reply-To: <20230327235936.414196-2-parav@nvidia.com>
Parav Pandit <parav@nvidia.com> writes:
> 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:
> v5->v6:
> - moved description close to introduction, it was in middle of
> queue data transfer description
> v2->v3:
> - new patch
> ---
> content.tex | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/content.tex b/content.tex
> index cff548a..5171c12 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -298,6 +298,9 @@ \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.}.
>
> +Each virtqueue is identified by a vq number or also referred
> +to as a virtqueue number; vq number range is from 0 to 65535.
> +
It would be nice to use the unabbreviated version first, and we could
also include "vqn", as it's in use during discussions:
Each virtqueue is identified by a virtqueue number, also referred to
as a vq number or vqn. The range of virtqueue numbers is 0 to 65535
inclusive.
> 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
--
The sound of a barking dog on a loop, a plane rises in the crystal blue.
---------------------------------------------------------------------
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-03-28 13:57 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 23:59 [virtio-comment] [PATCH v8 0/8] Rename queue index to queue number Parav Pandit
2023-03-27 23:59 ` [virtio-dev] " Parav Pandit
2023-03-27 23:59 ` [virtio-comment] [PATCH v8 1/8] content: Add vq number text Parav Pandit
2023-03-27 23:59 ` [virtio-dev] " Parav Pandit
2023-03-28 13:56 ` David Edmondson [this message]
2023-03-28 13:56 ` David Edmondson
2023-03-28 14:00 ` [virtio-comment] " Parav Pandit
2023-03-28 14:00 ` [virtio-dev] " Parav Pandit
2023-03-27 23:59 ` [virtio-comment] [PATCH v8 2/8] transport-pci: Refer to the vq by its number Parav Pandit
2023-03-27 23:59 ` [virtio-dev] " Parav Pandit
2023-03-28 13:58 ` [virtio-comment] " David Edmondson
2023-03-28 13:58 ` David Edmondson
2023-03-27 23:59 ` [virtio-comment] [PATCH v8 3/8] transport-mmio: Rename QueueNum register Parav Pandit
2023-03-27 23:59 ` [virtio-dev] " Parav Pandit
2023-03-28 14:01 ` [virtio-comment] " David Edmondson
2023-03-28 14:01 ` [virtio-dev] " David Edmondson
2023-03-27 23:59 ` [virtio-comment] [PATCH v8 4/8] transport-mmio: Refer to the vq by its number Parav Pandit
2023-03-27 23:59 ` [virtio-dev] " Parav Pandit
2023-03-28 14:05 ` [virtio-comment] " David Edmondson
2023-03-28 14:05 ` [virtio-dev] " David Edmondson
2023-03-27 23:59 ` [virtio-comment] [PATCH v8 5/8] transport-ccw: Rename queue depth/size to other transports Parav Pandit
2023-03-27 23:59 ` [virtio-dev] " Parav Pandit
2023-03-28 14:07 ` [virtio-comment] " David Edmondson
2023-03-28 14:07 ` [virtio-dev] " David Edmondson
2023-03-28 15:04 ` Parav Pandit
2023-03-28 15:04 ` [virtio-dev] " Parav Pandit
2023-03-28 16:16 ` David Edmondson
2023-03-28 16:16 ` [virtio-dev] " David Edmondson
2023-03-28 16:18 ` Parav Pandit
2023-03-28 16:18 ` [virtio-dev] " Parav Pandit
2023-03-27 23:59 ` [virtio-comment] [PATCH v8 6/8] transport-ccw: Refer to the vq by its number Parav Pandit
2023-03-27 23:59 ` [virtio-dev] " Parav Pandit
2023-03-27 23:59 ` [virtio-comment] [PATCH v8 7/8] virtio-net: Avoid duplicate receive queue example Parav Pandit
2023-03-27 23:59 ` [virtio-dev] " Parav Pandit
2023-03-27 23:59 ` [virtio-comment] [PATCH v8 8/8] virtio-net: Describe RSS using rss rq id Parav Pandit
2023-03-27 23:59 ` [virtio-dev] " Parav Pandit
2023-03-28 14:13 ` [virtio-comment] " David Edmondson
2023-03-28 14:13 ` David Edmondson
2023-03-28 13:53 ` [virtio-comment] Re: [virtio-dev] [PATCH v8 0/8] Rename queue index to queue number David Edmondson
2023-03-28 13:53 ` David Edmondson
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=m2bkkdc734.fsf@oracle.com \
--to=david.edmondson@oracle.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.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 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.