Title Resolve Issue #163: Bring consistency to identify a virtuque by number
Description
Please vote Yes if you agree with all of the following.
If you disagree, please vote No.
If you don't have an opinion, please vote Abstain.

I move that:
The TC agrees to resolve the following specification issue:
Issue #163: Bring consistency to identify a virtuque by number
--------------------------------------
Problem statement:

1. Currently, a virtqueue is identified between the 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:
Use virtqueue index description and rename MMIO register as QueueSize.

Patch to vote: https://lists.oasis-open.org/archives/virtio-comment/202305/msg00101.html
Patch for maintainer to merge for automation: https://lore.kernel.org/virtio-comment/20230505014614.571520-1-parav@nvidia.com/
--------------------------------------

The TC accepts the following proposed changes to the specification:
--------------------------------------
https://lists.oasis-open.org/archives/virtio-comment/202305/msg00101.html
--------------------------------------

The TC agrees to include the above change(s) in specification version(s) "virtio-v1.3-cs01", and future versions of the
specification.

--------------------------------------

Reminder: A Voting Member must be active in a TC to maintain voting rights.  As
the Virtio TC has adopted a standing rule to conduct business only by
electronic ballot, without Meetings, a Voting Member who fails to cast a ballot
in two consecutive Work Product Ballots loses his or her voting rights at the
close of the second ballot missed.

--------------------------------------
Ballot Options Ballot has closed
[ ] Yes
[ ] No
[ ] Abstain
Opening Date Thu, May 11 2023 12:30 pm EDT
Closing Date Thu, May 18 2023 12:30 pm EDT
Ballot has closed.

Referenced Items