Updating documents of D-release.

[kvmfornfv.git] / docs / design / kvmfornfv_design.rst

diff --git a/docs/design/kvmfornfv_design.rst b/docs/design/kvmfornfv_design.rst
index 54dcd12..765f412 100644 (file)
--- a/docs/design/kvmfornfv_design.rst
+++ b/docs/design/kvmfornfv_design.rst
@@ -1,24 +1,9 @@
 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
 .. http://creativecommons.org/licenses/by/4.0
 
-============
-Introduction
-============
-
-**Purpose**:
-
- This document provides an overview of the areas that can be addressed to
- enhance the KVM Hypervisor for NFV. It is intended to capture and convey the
- significant changes which have been made on the KVM Hypervisor.
-
-
-===================
-Project description
-===================
-
-The NFV hypervisors provide crucial functionality in the NFV
-Infrastructure(NFVI).The existing hypervisors, however, are not necessarily
-designed or targeted to meet the requirements for the NFVI.
+==========================
+KVM4NFV design description
+==========================
 
 This design focuses on the enhancement of following area for KVM Hypervisor
 
@@ -27,10 +12,6 @@ This design focuses on the enhancement of following area for KVM Hypervisor
    * Minimal packet latency variation for data-plane VNFs
 * Fast live migration
 
-While these items require software development and/or specific hardware features
-there are also some adjustments that need to be made to system configuration
-information, like hardware, BIOS, OS, etc.
-
 **Minimal Interrupt latency variation for data plane VNFs**
 
 Processing performance and latency depend on a number of factors, including
@@ -65,9 +46,9 @@ on KVM:
 
 .. Figure:: kvm1.png
 
-=====================
+
 Design Considerations
-=====================
+---------------------
 
 The latency variation and jitters can be minimized with the below
 steps (with some in parallel):
@@ -92,9 +73,9 @@ steps (with some in parallel):
     6. Measure latencies intensively. We leverage the existing testing methods.
        OSADL, for example, defines industry tests for timing correctness.
 
-====================
+
 Goals and Guidelines
-====================
+--------------------
 
 The output of this project will provide :
 
@@ -110,9 +91,9 @@ The output of this project will provide :
 
     4. Performance and interrupt latency measurement tools
 
-=========
+
 Test plan
-=========
+---------
 
 The tests that need to be conducted to make sure that all components from OPNFV
 meet the requirement are mentioned below:
@@ -131,7 +112,7 @@ interrupt handled in the VNF.
 
 .. Figure:: DeviceInterruptTest.png
 
-**Packet forwarding (DPDK OVS)**:A packet is sent from TC (Traffic Generator)
+**Packet forwarding (DPDK OVS)**:A packet is sent from TG (Traffic Generator)
 to a VNF.  The VNF, after processing the packet, forwards the packet to another
 NIC and in the end the packet is received by the traffic generator. The test
 check the latency from the packet is sent out by the TC to the time the packet
@@ -148,8 +129,8 @@ packet forwarding scenario.
 
 .. Figure:: Bare-metalPacketForwarding.png
 
-=========
+----------
 Reference
-=========
+----------
 
 https://wiki.opnfv.org/display/kvm/