All of lore.kernel.org
 help / color / mirror / Atom feed
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 v10 1/8] content: Add vq number text
Date: Thu, 30 Mar 2023 09:44:32 +0200	[thread overview]
Message-ID: <87355mhee7.fsf@redhat.com> (raw)
In-Reply-To: <20230329212341.465843-2-parav@nvidia.com>

On Thu, Mar 30 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:
> 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(+)

Reviewed-by: Cornelia Huck <cohuck@redhat.com>


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: 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 v10 1/8] content: Add vq number text
Date: Thu, 30 Mar 2023 09:44:32 +0200	[thread overview]
Message-ID: <87355mhee7.fsf@redhat.com> (raw)
In-Reply-To: <20230329212341.465843-2-parav@nvidia.com>

On Thu, Mar 30 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:
> 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(+)

Reviewed-by: Cornelia Huck <cohuck@redhat.com>


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2023-03-30  7:44 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 21:23 [virtio-comment] [PATCH v10 0/8] Rename queue index to queue number Parav Pandit
2023-03-29 21:23 ` [virtio-dev] " Parav Pandit
2023-03-29 21:23 ` [virtio-comment] [PATCH v10 1/8] content: Add vq number text Parav Pandit
2023-03-29 21:23   ` [virtio-dev] " Parav Pandit
2023-03-30  7:44   ` Cornelia Huck [this message]
2023-03-30  7:44     ` [virtio-dev] " Cornelia Huck
2023-03-29 21:23 ` [virtio-comment] [PATCH v10 2/8] transport-pci: Refer to the vq by its number Parav Pandit
2023-03-29 21:23   ` [virtio-dev] " Parav Pandit
2023-03-30 17:10   ` [virtio-comment] " Halil Pasic
2023-03-30 17:10     ` [virtio-dev] " Halil Pasic
2023-03-30 19:00     ` Parav Pandit
2023-03-30 19:00       ` [virtio-dev] " Parav Pandit
2023-03-29 21:23 ` [virtio-comment] [PATCH v10 3/8] transport-mmio: Rename QueueNum register Parav Pandit
2023-03-29 21:23   ` [virtio-dev] " Parav Pandit
2023-03-29 21:23 ` [virtio-comment] [PATCH v10 4/8] transport-mmio: Refer to the vq by its number Parav Pandit
2023-03-29 21:23   ` [virtio-dev] " Parav Pandit
2023-03-29 21:23 ` [virtio-comment] [PATCH v10 5/8] transport-ccw: Rename queue depth/size to other transports Parav Pandit
2023-03-29 21:23   ` [virtio-dev] " Parav Pandit
2023-03-29 21:23 ` [virtio-comment] [PATCH v10 6/8] transport-ccw: Refer to the vq by its number Parav Pandit
2023-03-29 21:23   ` [virtio-dev] " Parav Pandit
2023-03-30  7:48   ` [virtio-comment] " Cornelia Huck
2023-03-30  7:48     ` [virtio-dev] " Cornelia Huck
2023-03-29 21:23 ` [virtio-comment] [PATCH v10 7/8] virtio-net: Avoid duplicate receive queue example Parav Pandit
2023-03-29 21:23   ` [virtio-dev] " Parav Pandit
2023-03-30  7:53   ` [virtio-comment] " Cornelia Huck
2023-03-30  7:53     ` [virtio-dev] " Cornelia Huck
2023-03-29 21:23 ` [virtio-comment] [PATCH v10 8/8] virtio-net: Describe RSS using rss rq id Parav Pandit
2023-03-29 21:23   ` [virtio-dev] " Parav Pandit
2023-03-30  9:17   ` [virtio-comment] " Cornelia Huck
2023-03-30  9:17     ` [virtio-dev] " Cornelia Huck
2023-04-03 22:29     ` [virtio-comment] " Parav Pandit
2023-04-03 22:29       ` [virtio-dev] " Parav Pandit
2023-04-04  8:15       ` [virtio-comment] " Cornelia Huck
2023-04-04  8:15         ` [virtio-dev] " Cornelia Huck
2023-04-04 16:11         ` Parav Pandit
2023-04-04 16:11           ` [virtio-dev] " Parav Pandit
2023-03-30 17:11 ` [virtio-comment] Re: [virtio-dev] [PATCH v10 0/8] Rename queue index to queue number Halil Pasic
2023-03-30 17:11   ` Halil Pasic
2023-03-30 19:13   ` [virtio-comment] " Parav Pandit
2023-03-30 19:13     ` Parav Pandit
2023-04-04  1:36     ` [virtio-comment] " Halil Pasic
2023-04-04  1:36       ` Halil Pasic
2023-04-04  2:57       ` [virtio-comment] " Parav Pandit
2023-04-04  2:57         ` Parav Pandit
2023-04-04  6:33         ` [virtio-comment] " Michael S. Tsirkin
2023-04-04  6:33           ` Michael S. Tsirkin
2023-04-04 16:44           ` [virtio-comment] " Halil Pasic
2023-04-04 16:44             ` [virtio-dev] " Halil Pasic
2023-04-04  7:07         ` Michael S. Tsirkin
2023-04-04  7:07           ` Michael S. Tsirkin
2023-04-04 15:55           ` [virtio-comment] " Halil Pasic
2023-04-04 15:55             ` Halil Pasic
2023-04-04 16:08             ` [virtio-comment] " Cornelia Huck
2023-04-04 16:08               ` [virtio-dev] " Cornelia Huck
2023-04-04  7:13         ` Michael S. Tsirkin
2023-04-04  7:13           ` Michael S. Tsirkin
2023-03-31  8:13   ` [virtio-comment] " Cornelia Huck
2023-03-31  8:13     ` Cornelia Huck
2023-04-04  6:34     ` [virtio-comment] " Michael S. Tsirkin
2023-04-04  6:34       ` 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=87355mhee7.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: 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.