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: VIRTIO-160: clarify mergeable buffer use -------------------------------------- Description of how devices use mergeable buffers is not clear. The device clauses seem to use "descriptors" and buffers interchangeably while they are not the same. Further, the text seems to imply device should only use multiple buffers if a packet does not fit in a single one, but never actually says so. -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- Let's just make the spec match this reality - if devices ever want more flexibility, we can add a feature bit. Further, correct all misuses of a "descriptor" to "buffer" as thatis the entity that is being merged. https://lists.oasis-open.org/archives/virtio/201703/msg00009.html -------------------------------------- The TC agrees to include the above change(s) in specification version(s) "virtio 1.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. --------------------------------------
