virtio — archive

[Michael S. Tsirkin <mst@redhat.com>]

On Tue, Jan 30, 2018 at 11:16:59AM +0100, Cornelia Huck wrote: > On Tue, 23 Jan 2018 02:01:03 +0200 > "Michael S. Tsirkin" <mst@redhat.com> wrote: > > > Document buffer used len and use that terminology everywhere in the > > generic section. > > > > Signed-off-by: Michael S. Tsirkin <mst@redhat.com> > > --- > > content.tex | 39 ++++++++++++++++++++ ------------------- > > 1 file changed, 20 insertions(+), 19 deletions(-) > > > > diff --git a/content.tex b/content.tex > > index 3b4579e..4350ecf 100644 > > --- a/content.tex > > +++ b/content.tex > > @@ -242,7 +242,8 @@ a used buffer to the queue - i.e. lets the driver > > know by marking the buffer as used. Device can then trigger > > a device event - i.e. send an interrupt to the driver. > > > > -For queue operation detail, see \ref{sec:Basic Facilities of a Virtio Device / Split Virtqueues}~\nameref{sec:Basic Facilities of a Virtio Device / Split Virtqueues}. > > Why are you dropping this? That chapter follows immediately so the link is not helpful and it just looks weird: see split virtqueues - split virtqueues. I'll add text to description to mention this. > > +Device reports the number of bytes it has written to memory for > > +each buffer it uses. This is referred to as ``used length''. > > > > \input{split-ring.tex} > > > > Otherwise, using the term "used length" looks good.