diff options
| author | mstsirkin <mstsirkin@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652> | 2015-10-11 14:55:13 +0000 |
|---|---|---|
| committer | mstsirkin <mstsirkin@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652> | 2015-10-11 14:55:13 +0000 |
| commit | 15d8b243843e164e1914b5a7b6d633fda2e87351 (patch) | |
| tree | 903172d5bbb50fd1f8c09813bbab7304ee311e1d | |
| parent | 6233eaefd1a6207d6298b924da0aa96350b468ab (diff) | |
virtqueues: fix trivial typo
Signed-off-by: Greg Kurz <gkurz@linux.vnet.ibm.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio/branches/v1.0@540 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
| -rw-r--r-- | content.tex | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content.tex b/content.tex index d989d98..bc7455b 100644 --- a/content.tex +++ b/content.tex @@ -522,7 +522,7 @@ VRING_AVAIL_F_NO_INTERRUPT, but the layout and value were identical. If the VIRTIO_F_EVENT_IDX feature bit is not negotiated, the \field{flags} field in the available ring offers a crude mechanism for the driver to inform the device that it doesn't want interrupts when buffers are used. Otherwise -\field{used_event} is a more performant alterative where the driver +\field{used_event} is a more performant alternative where the driver specifies how far the device can progress before interrupting. Neither of these interrupt suppression methods are reliable, as they |