From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: virtio-dev@lists.oasis-open.org, pasic@linux.ibm.com,
cohuck@redhat.com, virtio-comment@lists.oasis-open.org,
shahafs@nvidia.com
Subject: [virtio-dev] Re: [PATCH v4 0/8] Rename queue index to queue number
Date: Wed, 22 Mar 2023 19:04:28 -0400 [thread overview]
Message-ID: <20230322190416-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230322215243.249524-1-parav@nvidia.com>
On Wed, Mar 22, 2023 at 11:52:35PM +0200, Parav Pandit wrote:
> 1. Currently, virtqueue is identified between driver and device
> interchangeably using either number of index terminology.
>
> 2. Between PCI and MMIO transport the queue size (depth) is
> defined as queue_size and QueueNum respectively.
>
> To avoid confusion and to have consistency, unify them to use as Number.
Looks good, some comments on 8/8.
> Solution:
> a. Use virtqueue number description, and rename MMIO register as QueueSize.
> b. Replace virtqueue index to virtqueue number
> c. RSS area of virtio net has inherited some logic, describe it
> using abstract rq_handle.
>
> Patch summary:
> patch-1 introduce vq number as generic term
> patch-2 renames index to number for pci transport
> patch-3 renames mmio register from Num to Size
> patch-4 renames index to number for mmio transport
> patch-5 renames num field to size for ccw transport
> patch-6 renames index field to queue_select for ccw transport
> patch-7 for virtio-net removes duplicate example from requirements
> patch-8 for virtio-net updates rss description to use vq number
>
> This series only improves the documentation, it does not change any
> transport or device functionality.
>
> Please review.
> This series fixes the issue [1].
>
> [1] https://github.com/oasis-tcs/virtio-spec/issues/163
>
> ---
> changelog:
> v3->v4:
> - moved note to comment for ccw
> - renamed rq_handle to rss_rq_id
> - moved rss_rq_id next to rss_config structure
> - define rss_config structure using rss_rq_id
> v2->v3:
> - addressed comments from Michael
> - added previous definitions for ccw fields
> - moved rq_handle definition before using it
> - added first patch to describe vq number
> - updated pci for available buffer notification section
> v1->v2:
> - added patches for virtio net for rss area
> - added patches for covering ccw transport
> - added missing entries to refer in mmio transport
>
> Parav Pandit (8):
> content: Add vq number text
> transport-pci: Refer to the vq by its number
> transport-mmio: Rename QueueNum register
> transport-mmio: Refer to the vq by its number
> transport-ccw: Rename queue depth/size to other transports
> transport-ccw: Refer to the vq by its number
> virtio-net: Avoid duplicate receive queue example
> virtio-net: Describe RSS using receive queue handle
>
> content.tex | 3 ++
> device-types/net/description.tex | 29 ++++++++++++-----
> transport-ccw.tex | 27 ++++++++-------
> transport-mmio.tex | 56 +++++++++++++++++++-------------
> transport-pci.tex | 14 ++++----
> 5 files changed, 81 insertions(+), 48 deletions(-)
>
> --
> 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
prev parent reply other threads:[~2023-03-22 23:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 21:52 [virtio-dev] [PATCH v4 0/8] Rename queue index to queue number Parav Pandit
2023-03-22 21:52 ` [virtio-dev] [PATCH v4 1/8] content: Add vq number text Parav Pandit
2023-03-22 21:52 ` [virtio-dev] [PATCH v4 2/8] transport-pci: Refer to the vq by its number Parav Pandit
[not found] ` <68fc71b0-2026-fd99-22f3-d0313e597373@nvidia.com>
2023-03-27 23:19 ` [virtio-dev] RE: [virtio-comment] " Parav Pandit
2023-03-22 21:52 ` [virtio-dev] [PATCH v4 3/8] transport-mmio: Rename QueueNum register Parav Pandit
2023-03-22 21:52 ` [virtio-dev] [PATCH v4 4/8] transport-mmio: Refer to the vq by its number Parav Pandit
2023-03-22 21:52 ` [virtio-dev] [PATCH v4 5/8] transport-ccw: Rename queue depth/size to other transports Parav Pandit
2023-03-22 21:52 ` [virtio-dev] [PATCH v4 6/8] transport-ccw: Refer to the vq by its number Parav Pandit
2023-03-22 21:52 ` [virtio-dev] [PATCH v4 7/8] virtio-net: Avoid duplicate receive queue example Parav Pandit
2023-03-22 21:52 ` [virtio-dev] [PATCH v4 8/8] virtio-net: Describe RSS using receive queue handle Parav Pandit
2023-03-22 23:03 ` [virtio-dev] " Michael S. Tsirkin
2023-03-22 23:47 ` [virtio-dev] " Parav Pandit
2023-03-22 23:04 ` Michael S. Tsirkin [this message]
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=20230322190416-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=parav@nvidia.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