From: Cornelia Huck <cohuck@redhat.com> To: Parav Pandit <parav@nvidia.com>, mst@redhat.com, virtio-dev@lists.oasis-open.org, pasic@linux.ibm.com Cc: sgarzare@redhat.com, virtio-comment@lists.oasis-open.org, shahafs@nvidia.com, Parav Pandit <parav@nvidia.com> Subject: [virtio-dev] Re: [PATCH v9 1/8] content: Add vq number text Date: Wed, 29 Mar 2023 11:01:06 +0200 [thread overview] Message-ID: <87zg7wlynh.fsf@redhat.com> (raw) In-Reply-To: <20230328201754.440974-2-parav@nvidia.com> On Tue, Mar 28 2023, Parav Pandit <parav@nvidia.com> wrote: > 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: > 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..3766bf9 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.}. > > +Each virtqueue is identified by a vq number or also referred > +to as a virtqueue number; I think "identified by a vq number (also referred to as a virtqueue number)" would read better. > vq number range is from 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 --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
WARNING: multiple messages have this Message-ID (diff)
From: Cornelia Huck <cohuck@redhat.com> To: Parav Pandit <parav@nvidia.com>, mst@redhat.com, virtio-dev@lists.oasis-open.org, pasic@linux.ibm.com Cc: sgarzare@redhat.com, virtio-comment@lists.oasis-open.org, shahafs@nvidia.com, Parav Pandit <parav@nvidia.com> Subject: [virtio-comment] Re: [PATCH v9 1/8] content: Add vq number text Date: Wed, 29 Mar 2023 11:01:06 +0200 [thread overview] Message-ID: <87zg7wlynh.fsf@redhat.com> (raw) In-Reply-To: <20230328201754.440974-2-parav@nvidia.com> On Tue, Mar 28 2023, Parav Pandit <parav@nvidia.com> wrote: > 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: > 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..3766bf9 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.}. > > +Each virtqueue is identified by a vq number or also referred > +to as a virtqueue number; I think "identified by a vq number (also referred to as a virtqueue number)" would read better. > vq number range is from 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 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/
next prev parent reply other threads:[~2023-03-29 9:01 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-28 20:17 [virtio-dev] [PATCH v9 0/8] Rename queue index to queue number Parav Pandit 2023-03-28 20:17 ` [virtio-comment] " Parav Pandit 2023-03-28 20:17 ` [virtio-dev] [PATCH v9 1/8] content: Add vq number text Parav Pandit 2023-03-28 20:17 ` [virtio-comment] " Parav Pandit 2023-03-29 9:01 ` Cornelia Huck [this message] 2023-03-29 9:01 ` [virtio-comment] " Cornelia Huck 2023-03-28 20:17 ` [virtio-dev] [PATCH v9 2/8] transport-pci: Refer to the vq by its number Parav Pandit 2023-03-28 20:17 ` [virtio-comment] " Parav Pandit 2023-03-29 9:06 ` [virtio-dev] " Cornelia Huck 2023-03-29 9:06 ` [virtio-comment] " Cornelia Huck 2023-03-28 20:17 ` [virtio-dev] [PATCH v9 3/8] transport-mmio: Rename QueueNum register Parav Pandit 2023-03-28 20:17 ` [virtio-comment] " Parav Pandit 2023-03-29 9:15 ` [virtio-dev] " Cornelia Huck 2023-03-29 9:15 ` [virtio-comment] " Cornelia Huck 2023-03-29 12:59 ` [virtio-dev] " Parav Pandit 2023-03-29 12:59 ` [virtio-comment] " Parav Pandit 2023-03-29 13:16 ` [virtio-dev] " Cornelia Huck 2023-03-29 13:16 ` [virtio-comment] " Cornelia Huck 2023-03-28 20:17 ` [virtio-dev] [PATCH v9 4/8] transport-mmio: Refer to the vq by its number Parav Pandit 2023-03-28 20:17 ` [virtio-comment] " Parav Pandit 2023-03-29 9:18 ` [virtio-dev] " Cornelia Huck 2023-03-29 9:18 ` [virtio-comment] " Cornelia Huck 2023-03-28 20:17 ` [virtio-dev] [PATCH v9 5/8] transport-ccw: Rename queue depth/size to other transports Parav Pandit 2023-03-28 20:17 ` [virtio-comment] " Parav Pandit 2023-03-29 9:23 ` [virtio-dev] " Cornelia Huck 2023-03-29 9:23 ` [virtio-comment] " Cornelia Huck 2023-03-28 20:17 ` [virtio-dev] [PATCH v9 6/8] transport-ccw: Refer to the vq by its number Parav Pandit 2023-03-28 20:17 ` [virtio-comment] " Parav Pandit 2023-03-29 9:30 ` [virtio-dev] " Cornelia Huck 2023-03-29 9:30 ` [virtio-comment] " Cornelia Huck 2023-03-29 13:01 ` [virtio-dev] " Parav Pandit 2023-03-29 13:01 ` [virtio-comment] " Parav Pandit 2023-03-29 13:18 ` [virtio-dev] " Cornelia Huck 2023-03-29 13:18 ` [virtio-comment] " Cornelia Huck 2023-03-28 20:17 ` [virtio-dev] [PATCH v9 7/8] virtio-net: Avoid duplicate receive queue example Parav Pandit 2023-03-28 20:17 ` [virtio-comment] " Parav Pandit 2023-03-28 20:17 ` [virtio-dev] [PATCH v9 8/8] virtio-net: Describe RSS using rss rq id Parav Pandit 2023-03-28 20:17 ` [virtio-comment] " 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=87zg7wlynh.fsf@redhat.com \ --to=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: linkBe 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.