From 82ef43b92ab7d56f486cb31b2e0b26ce51bd1ea8 Mon Sep 17 00:00:00 2001 From: rusty Date: Mon, 10 Feb 2014 10:30:46 +0000 Subject: patch feedback-5.patch git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@215 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652 --- abstract.tex | 2 +- introduction.tex | 7 ++++--- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/abstract.tex b/abstract.tex index b42a0b6..186fb81 100644 --- a/abstract.tex +++ b/abstract.tex @@ -1,7 +1,7 @@ This document describes the specifications of the “virtio” family of devices. These devices are found in virtual environments, yet by design they are not all that different from physical devices, and this -document treats them as such. This allows the guest to use standard +document treats them as such. This similarity allows the guest to use standard drivers and discovery mechanisms. The purpose of virtio and this specification is that virtual diff --git a/introduction.tex b/introduction.tex index 83b01f0..8e08d02 100644 --- a/introduction.tex +++ b/introduction.tex @@ -13,14 +13,15 @@ inter-guest communication) requires copying. } Efficient: Virtio devices consist of rings of descriptors - for input and output, which are neatly separated to avoid cache + for both input and output, which are neatly laid out to avoid cache effects from both driver and device writing to the same cache lines. Standard: Virtio makes no assumptions about the environment in which - it operates, beyond supporting the bus attaching the device. Virtio + it operates, beyond supporting the bus to which device is attached. + In this specification, virtio devices are implemented over PCI and other buses, and earlier drafts - been implemented on other buses not included in this spec. + have been implemented on other buses not included here. \footnote{The Linux implementation further separates the PCI virtio code from the specific virtio drivers: these drivers are shared with the non-PCI implementations (currently lguest and S/390). -- cgit v1.2.3