On Thu, 30 Jan 2014 18:10:23 +0200
"Michael S. Tsirkin" <> wrote:
> explicitly say driver/device or use passive form
> as appropriate.
>
>
Cc: Arun Subbarao <>
> Signed-off-by: Michael S. Tsirkin <>
> ---
> content.tex | 18 ++++++++++
--------
> 1 file changed, 10 insertions(+), 8 deletions(-)
>
> @@ -663,12 +664,12 @@ device), so we keep a counter of how many we've added:
> \subsubsection{Updating The Index Field}\label{sec:General Initialization And Device Operation / Device Operation / Supplying Buffers to The Device / Updating The Index Field}
>
> Once the index field of the virtqueue is updated, the device will
> -be able to access the descriptor chains we've created and the
> +be able to access the descriptor chains that driver created and the
s/driver/the driver/ ?
(also in various places below)
> memory they refer to. This is why a memory barrier is generally
> used before the index update, to ensure it sees the most up-to-date
> copy.
>
> -The index field always increments, and we let it wrap naturally at
> +The index field always increments, and wraps naturally at
> 65536:
>
> \begin{lstlisting}