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-dev] [PATCH v2 0/7] Rename queue index to queue number
Date: Tue, 21 Mar 2023 06:10:29 +0200 [thread overview]
Message-ID: <20230321041036.201439-1-parav@nvidia.com> (raw)
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.
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 renames index to number for pci transport
patch-2 renames mmio register from Num to Size
patch-3 renames index to number for mmio transport
patch-4 renames num field to size for ccw transport
patch-5 renames index field to queue_select for ccw transport
patch-6 for virtio-net removes duplicate example from requirements
patch-7 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:
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 (7):
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
device-types/net/description.tex | 26 +++++++++++----
transport-ccw.tex | 39 +++++++++++++++-------
transport-mmio.tex | 56 +++++++++++++++++++-------------
transport-pci.tex | 6 ++--
4 files changed, 84 insertions(+), 43 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
next reply other threads:[~2023-03-21 4:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 4:10 Parav Pandit [this message]
2023-03-21 4:10 ` [virtio-dev] [PATCH v2 1/7] transport-pci: Refer to the vq by its number Parav Pandit
2023-03-21 9:01 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-03-21 20:43 ` [virtio-dev] " Parav Pandit
2023-03-21 4:10 ` [virtio-dev] [PATCH v2 2/7] transport-mmio: Rename QueueNum register Parav Pandit
2023-03-21 4:10 ` [virtio-dev] [PATCH v2 3/7] transport-mmio: Refer to the vq by its number Parav Pandit
2023-03-21 4:10 ` [virtio-dev] [PATCH v2 4/7] transport-ccw: Rename queue depth/size to other transports Parav Pandit
2023-03-21 4:10 ` [virtio-dev] [PATCH v2 5/7] transport-ccw: Refer to the vq by its number Parav Pandit
2023-03-21 8:46 ` [virtio-dev] " Michael S. Tsirkin
2023-03-21 4:10 ` [virtio-dev] [PATCH v2 6/7] virtio-net: Avoid duplicate receive queue example Parav Pandit
2023-03-21 4:10 ` [virtio-dev] [PATCH v2 7/7] virtio-net: Describe RSS using receive queue handle Parav Pandit
2023-03-21 8:55 ` [virtio-dev] " Michael S. Tsirkin
2023-03-21 20:54 ` [virtio-dev] " Parav Pandit
2023-03-21 21:15 ` Parav Pandit
2023-03-21 9:05 ` [virtio-dev] Re: [PATCH v2 0/7] Rename queue index to queue number Michael S. Tsirkin
2023-03-21 20:57 ` [virtio-dev] " 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=20230321041036.201439-1-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