OASIS Virtual I/O Device (VIRTIO) TC

Add some clarification to the head of the virtqueue section outlining how the vring/virtio_ring terminology is used throughout the specification. Reported-by: Holm Rauchfuss <holm.rauchfuss@huawei.com> Signed-off-by: Paul Mundt <paul.mundt@huawei.com> --- diff --git a/content.tex b/content.tex index c804c53..da30993 100644 --- a/content.tex +++ b/content.tex @@ -195,11 +195,12 @@ result. section{Virtqueues}label{sec:Basic Facilities of a Virtio Device / Virtqueues} The mechanism for bulk data transport on virtio devices is -pretentiously called a virtqueue. Each device can have zero or more -virtqueues: for example, the simplest network device has one for -transmit and one for receive. Each queue has a 16-bit queue size -parameter, which sets the number of entries and implies the total size -of the queue. +pretentiously called a virtqueue; the terms vring and virtio_ring +are also used interchangeably to refer to the in-memory format of the +virtqueue itself. Each device can have zero or more virtqueues: for example, +the simplest network device has one for transmit and one for receive. +Each queue has a 16-bit queue size parameter, which sets the number of +entries and implies the total size of the queue. Each virtqueue consists of three parts:

Paul Mundt <Paul.Mundt@huawei.com> writes: > Add some clarification to the head of the virtqueue section outlining > how the vring/virtio_ring terminology is used throughout the > specification. Here's an alternative, which simply uses consistent naming. This is slightly cleaner of course, but is a bit of a pain for those used to the legacy names. So it needs addition of the legacy sections mentioning that, but I'll wait until MST merges his stuff into master. MST? Thanks, Rusty.