Should the TC accept changes listed in the description to resolve issue 28,
for inclusion in specification version(s) "virtio-v1.1-cs01", and future versions of the specification?
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 #28: packed-ring: fix queue_size for pci
--------------------------------------
PCI is the only transport that specifies that queue size is a power of 2
at the transport level. That's now incorrect with introduction of
the packed ring. As a minimal change, let's just document the
two options.
And going back to packed ring, no transport actually has a reason
to enforce a power of two size. So let's drop this from the text.
--------------------------------------
The TC accepts the following proposed changes to the specification:
--------------------------------------
https://lists.oasis-open.org/archives/virtio/201811/msg00015.html
--------------------------------------
The TC agrees to include the above change(s) in specification version(s) "virtio-v1.1-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.
--------------------------------------
|