On Tue, Feb 11, 2014 at 12:50:11PM +0000, RAUCHFUSS Holm wrote:
> Hi,
>
> I was reading the VIRTIO specification 1.0 draft (and looking in parallel into the implementation in Linux). I noticed that the draft uses the term virtqueue to describe essentially virtio_ring (or vring, as used in the associated code examples) in chapter 2.4. This is even more obvious when reading the white paper "virtio: Towards a De-Facto Standard For Virtual I/O Devices" before. Is it intended that virtqueue now equals virtio_ring? In any case, maybe the language can be cleaned up a bit; using vring*, VRING_* and virtio_ring for virtqueue without any prior notion/introduction of virtio_ring is a little bit confusing (if only reading the spec and not knowing the history of virtio).
>
>
> Regards,
>
> Holm
This is a good point, thanks!
I have created jira issue 60
https://tools.oasis-open.org/issues/browse/VIRTIO-60to address this comment.
> This publicly archived list offers a means to provide input to the
> OASIS Virtual I/O Device (VIRTIO) TC.
>
> In order to verify user consent to the Feedback License terms and
> to minimize spam in the list archive, subscription is required
> before posting.
>
> Subscribe:
virtio-comment-subscribe@lists.oasis-open.org> Unsubscribe:
virtio-comment-unsubscribe@lists.oasis-open.org> List help:
virtio-comment-help@lists.oasis-open.org> List archive:
https://lists.oasis-open.org/archives/virtio-comment/> Feedback License:
https://www.oasis-open.org/who/ipr/feedback_license.pdf> List Guidelines:
https://www.oasis-open.org/policies-guidelines/mailing-lists> Committee:
https://www.oasis-open.org/committees/virtio/> Join OASIS:
https://www.oasis-open.org/join/