diff --git a/doc/dts_gsg/config.rst b/doc/dts_gsg/config.rst
deleted file mode 100644
index e02d152..0000000
--- a/doc/dts_gsg/config.rst
+++ /dev/null
@@ -1,336 +0,0 @@
-Configuring DPDK Test Suite 
-===========================
-
-DPDK Test Suite command line
-----------------------------
-
-DPDK Test Suite supports multiple parameters and these parameters, which will select different of working mode of test framework. In the meantime, DPDK Test Suite can work with none parameter, then  every parameter will set to its default value.
-For Example, please see specific usage, you can get these information via DPDK Test Suite help messages.
-
-.. code-block:: console
-
-   usage: main.py [-h] [--config-file CONFIG_FILE] [--git GIT] [--patch PATCH]
-                  [--snapshot SNAPSHOT] [--output OUTPUT] [-s] [-r] [-p PROJECT]
-                  [--suite-dir SUITE_DIR] [-t TEST_CASES] [-d DIR] [-v]
-                  [--virttype VIRTTYPE] [--debug] [--debugcase] [--re_run RE_RUN]
-                  [--commands COMMANDS]
-
-
-DPDK Test Suite supports the following parameters:
-
-.. table::
-
-    +---------------------------+---------------------------------------------------+------------------+
-    | parameter                 | description                                       | Default Value    |
-    +---------------------------+---------------------------------------------------+------------------+
-    | -h,--help                 | show this help message and exit                   |                  |
-    +---------------------------+---------------------------------------------------+------------------+
-    | --config-file CONFIG_FILE | configuration file that describes the test cases, | execution.cfg    |
-    |                           | DUTs and targets                                  |                  |
-    +---------------------------+---------------------------------------------------+------------------+
-    | --git GIT                 | Indicate git label to use as input                | None             |
-    +---------------------------+---------------------------------------------------+------------------+
-    | --patch PATCH             | apply a patch to the package under test           | None             |
-    +---------------------------+---------------------------------------------------+------------------+
-    | --snapshot SNAPSHOT       | snapshot .tgz file to use as input                | dep/dpdk.tar.gz  |
-    +---------------------------+---------------------------------------------------+------------------+
-    | --output OUTPUT           | Output directory where DPDK Test Suite log and    | output           |
-    |                           | result saved                                      |                  |
-    +---------------------------+---------------------------------------------------+------------------+
-    | -s --skip-setup           | Skips all possible setup steps done on both DUT   |                  |
-    |                           | and tester boards.                                |                  |
-    +---------------------------+---------------------------------------------------+------------------+
-    | -r                        | Reads the DUT configuration from a cache. If not  |                  |
-    |                           | specified, the DUT configuration will be          |                  |
-    |                           | calculated as usual and cached.                   |                  |
-    +---------------------------+---------------------------------------------------+------------------+
-    | -p PROJECT                | Specify that which project will be tested dpdk    |                  |
-    | --project PROJECT         |                                                   |                  |
-    +---------------------------+---------------------------------------------------+------------------+
-    | -t TEST_CASES             | Executes only the followings test cases           | None             |
-    | [TEST_CASES ...]          |                                                   |                  |
-    | --test-cases              |                                                   |                  |
-    | TEST_CASES                |                                                   |                  |
-    | [TEST_CASES ...]          |                                                   |                  |
-    +---------------------------+---------------------------------------------------+------------------+
-    | -d DIR --dir DIR          | Output directory where dpdk package is extracted  | dpdk             |
-    +---------------------------+---------------------------------------------------+------------------+
-    | --suite-dir               | Test suite directory where test suites will be    | tests            |
-    |                           | imported                                          |                  |
-    +---------------------------+---------------------------------------------------+------------------+
-    | -v, --verbose             | Enable verbose output, all log shown on screen    |                  |
-    +---------------------------+---------------------------------------------------+------------------+
-    | --virttype                | Set virtualization hypervisor type. Support kvm   |                  |
-    |                           | and libvirtd by now.                              |                  |
-    +---------------------------+---------------------------------------------------+------------------+
-    | --debug                   | Enable debug mode, running process can be         |                  |
-    |                           | interrupted and enter debug mode.                 |                  |
-    +---------------------------+---------------------------------------------------+------------------+
-    | --debugcase               | Enter into debug mode before running every test   |                  |
-    |                           | case.                                             |                  |
-    +---------------------------+---------------------------------------------------+------------------+
-    | --re_run TIMES            | Rerun failed test cases for stable result         | 0                |
-    +---------------------------+---------------------------------------------------+------------------+
-    | --commands COMMANDS       | Run self assigned commands at different stages of |                  |
-    |                           | execution. Format is [commands]:dut|tester:pre-   |                  |
-    |                           | init|post-init:check|ignore                       |                  |
-    |                           | E.g. [/root/setup.sh]:dut:pre-init:check          |                  |
-    +---------------------------+---------------------------------------------------+------------------+
-
-Please see more information about some critical parameters as the following:
-
-**--config-file**
-
-DPDK Test Suite configure file defines some critical parameters.  It must contain the DUT CRB IP address, wish list of test suites, DPDK target information and test mode parameter.
-
-**--git**
-
-When we use –-git parameter, DPDK Test Suite will clone the source code from dpdk.org git repository, then checkout branch specified by the parameter. 
-
-**--patch**
-
-DPDK Test Suite also support apply specified patch list by --patch parameter before build DPDK packet. 
-
-**--skip-setup**
-
-If DPDK source code doesn’t changed, you can use --skip-setup to skip unzip and compilation of DPDK source code, just reuse original source code. 
-
-**--project**
-
-Parameter –-project can load customized project model and do its own project initialization.
-
-**--output**
-
-If we perform multiple validation at the same time, result files in output folder maybe overwritten. Then we can use –-output parameter to specify the output folder and save execution log and result files. This option will make sure that all test result will be stored in the different excel files and rst files, doesn’t conflict each other.
-
-.. note::
-   The current working folder of DPDK Test Suite is "DTS root directory"  and default output folder is “output”
-
-**--t**
-
-You can only run some specified cases in test suites.
-
-We can use parameter –-t to determine those cases.
-
-**--suite-dir**
-
-DPDK Test Suite support load suites from different folders, this will be helpful when there’s several projects existing in the same time. 
-
-**--verbose**
-
-DPDK Test Suite support verbose mode. When enable this mode, all log messages will be output on screen and helpful for debug.
-
-**--virttype**
-
-Choose virtualization hypervisor type. By now this configuration is useless.
-
-**--debug**
-
-DPDK Test Suite support debug mode. After keyboard ctrl+c message to DTS process, will run into this mode. User can do further debug by attached to sessions or call pdb module by interact interface.
-
-Debug interact support commands as below:
-
-.. code-block:: console
-
-    help(): show help message
-    list(): list all connected sessions
-    connect(name): connect to session directly
-    exit(): exit dts
-    quit(): quit debug mode and into normal mode
-    debug(): call python debug module
-
-**--debugcase**
-
-Another approach to run into debug mode. With this option on, DTS will hang and wait for user command before execution of each test case.
-
-**--re_run**
-
-Some cases may failed due to miscellaneous packets, rerun those test cases can generate the stable result.
-
-**--commands**
-
-Allow user specify some commands which can be executed on DUT or Tester in the process of DPDK Test Suite preparation.
-
-DPDK Release Preparation
-------------------------
-
-Firstly, you need to download the latest code from dpdk.org, then archive and compress it into zipped file. After that, please move this zipped file to DPDK Test Suite "dep" folder. Once launch test framework, DPDK Test Suite will copy this zipped file to root folder on DUT. Finally this source code zip file will be unzipped and built.
-
-.. code-block:: console
-
-    [root@tester dts]#  ls
-    [root@tester dts]#  conf dep doc dts executions framework nics output test_plans tests tools
-
-
-If enables patch option, DPDK Test Suite will also make patch the unzipped folder and compile it.
-
-.. code-block:: console
-
-   [root@tester dts]# ./dts --patch 1.patch --patch 2.patch
-
-Create your own execution configuration
----------------------------------------
-
-First of all, you must create a file named execution.cfg as below.
-
-.. code-block:: console
-
-   [Execution1]
-   crbs=192.168.1.1
-   test_suites=
-   hello_world,
-   l2fwd
-   targets=
-   x86_64-default-linuxapp-gcc,
-   parameters=nic_type=niantic:func=true
-   scenario=pf_passthrough
-
-*   crbs: IP address of the DUT CRB. The detail information of this CRB is defined in file crbs.py.
-*   test_suites:  defines list of test suites, which will plan to be executed.
-*   targets: list of DPDK targets to be tested.
-*   parameters: you can define multiple keywords
-*   scenario: Scenario of DPDK virtualization environment for this execution.
-
-    – nic_type : is the type of the NIC to use. The types are defined in the file settings.py.
-                 There's one special type named as **cfg**, which mean network information will be loaded from file.
-
-    – func=true run only functional test
-
-    – perf=true run only performance test
-
-Then please add the detail information about your CRB in **conf/crbs.conf** as follows:
-
-.. code-block:: console
-
-   [192.168.1.1]
-   dut_ip=192.168.1.1
-   dut_user=root
-   dut_passwd=
-   os=linux
-   tester_ip=192.168.1.2
-   tester_passwd=
-   ixia_group=group1
-   channels=4
-   bypass_core0=True
-
-
-.. table::
-
-    +-----------------+----------------------------------------------------+
-    | Item            | description                                        |
-    +-----------------+----------------------------------------------------+
-    | dut_ip          | IP address of DUT                                  |
-    +-----------------+----------------------------------------------------+
-    | dut_user        | UserName of DPDK Test Suite used to login into DUT |
-    +-----------------+----------------------------------------------------+
-    | dut_passwd      | Password of DPDK Test Suite used to login into DUT |
-    +-----------------+----------------------------------------------------+
-    | os              | Distribution of operation system                   |
-    +-----------------+----------------------------------------------------+
-    | tester_ip       | IP address of tester                               |
-    +-----------------+----------------------------------------------------+
-    | tester_passwd   | Password to login into Tester                      |
-    +-----------------+----------------------------------------------------+
-    | ixia_group      | IXIA group name for DUT                            |
-    +-----------------+----------------------------------------------------+
-    | channels        | number of memory channels for DPDK EAL             |
-    +-----------------+----------------------------------------------------+
-    | bypass_core0    | skip the first core when initialize DPDK           |
-    +-----------------+----------------------------------------------------+
-
-If you need to configure network topology, please add it in **conf/ports.cfg**, e.g.:
-
-.. code-block:: console
-
-   [192.168.1.1]
-   ports =
-       pci=0000:06:00.0,peer=0000:81:00.0;
-       pci=0000:06:00.1,peer=0000:81:00.1;
-       pci=0000:08:00.0,peer=IXIA:1.1;
-       pci=0000:08:00.1,peer=IXIA:1.2;
-
-.. table::
-
-    +-----------------+----------------------------------------------------+
-    | Item            | description                                        |
-    +-----------------+----------------------------------------------------+
-    | pci             | Device pci address of DUT                          |
-    +-----------------+----------------------------------------------------+
-    | peer            | Device pci address of Tester port which connected  |
-    |                 | to the DUT device                                  |
-    +-----------------+----------------------------------------------------+
-
-Launch DPDK Test Suite
-----------------------
-
-After we have prepared the zipped dpdk file and configuration file, just type the followed command “./dts”, it will start the validation process.
-
-DPDK Test Suite will create communication sessions first.
-
-.. code-block:: console
-
-   DUT 192.168.1.1
-   INFO: ssh root@192.168.1.1
-   INFO: ssh root@192.168.1.1
-   INFO: ssh root@192.168.1.2
-   INFO: ssh root@192.168.1.2
-
-
-Then copy snapshot zipped dpdk source code to DUT.
-
-.. code-block:: console
-
-   DTS_DUT_CMD: scp dep/dpdk.tar.gz root@192.168.1.1:
-
-Collect CPU core and network device information of DUT and tester.
-
-Automatically detect the network topology of DUT and tester.
-
-.. code-block:: console
-
-   DTS_TESTER_RESULT: DUT PORT MAP: [4, 5, 6, 7]
-
-Build dpdk source code and then setup the running environment. 
-
-.. code-block:: console
-
-   DTS_DUT_CMD: make -j install T=x86_64-native-linuxapp-gcc
-   DTS_DUT_CMD: awk '/Hugepagesize/ {print $2}' /proc/meminfo
-   DTS_DUT_CMD: awk '/HugePages_Total/ { print $2 }' /proc/meminfo
-   DTS_DUT_CMD: umount `awk '/hugetlbfs/ { print $2 }' /proc/mounts`
-   DTS_DUT_CMD: mkdir -p /mnt/huge
-   DTS_DUT_CMD: mount -t hugetlbfs nodev /mnt/huge
-   DTS_DUT_CMD: modprobe uio
-   DTS_DUT_CMD: rmmod -f igb_uio
-   DTS_DUT_CMD: insmod ./x86_64-native-linuxapp-gcc/kmod/igb_uio.ko
-   DTS_DUT_CMD: lsmod | grep igb_uio
-   DTS_DUT_CMD: usertools/dpdk_nic_bind.py --bind=igb_uio 08:00.0 08:00.1 0a:00.0 0a:00.1
-
-Begin the validation process of test suite.
-
-.. code-block:: console
-
-   TEST SUITE : TestCmdline
-                     INFO: NIC :        niantic
-       SUITE_DUT_CMD: make -j -C examples/cmdline
-       SUITE_DUT_CMD: ./examples/cmdline/build/app/cmdline -n 1 -c 0x2
-                               INFO: Test Case test_cmdline_sample_commands Begin
-
-
-Clean-up DUT and tester after all validation finished.
-
-.. code-block:: console
-
-        DTS_DUT_CMD: rmmod igb_uio
-        DTS_DUT_CMD: modprobe igb
-        DTS_DUT_CMD: modprobe ixgbe
-        DTS_DUT_CMD: modprobe e1000e
-        DTS_DUT_CMD: modprobe e1000
-        DTS_DUT_CMD: modprobe virtio_net
-     DTS_TESTER_CMD: rmmod igb_uio
-     DTS_TESTER_CMD: modprobe igb
-     DTS_TESTER_CMD: modprobe ixgbe
-     DTS_TESTER_CMD: modprobe e1000e
-     DTS_TESTER_CMD: modprobe e1000
-     DTS_TESTER_CMD: modprobe virtio_net
-
diff --git a/doc/dts_gsg/image/dts_result.png b/doc/dts_gsg/image/dts_result.png
index f39f5f8dc817066e3603c785f9d20ebe33bdce53..65e0ada586bfb5264eab02f7a6dedfe898e12849 100644
GIT binary patch
diff --git a/doc/dts_gsg/index.rst b/doc/dts_gsg/index.rst
index 0c84f46..aab4411 100644
--- a/doc/dts_gsg/index.rst
+++ b/doc/dts_gsg/index.rst
@@ -28,6 +28,7 @@
     (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
     OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
+=====================
 Getting Started Guide
 =====================
 
@@ -35,17 +36,5 @@ Getting Started Guide
     :maxdepth: 2
     :numbered:
 
-    intro
-    sys_reqs
-    config
-    review
-    tutorial
-    virtualization
-    scenario
-    multiple_vm
-    pktgen_prog_guide
-    migrate_from_etgen_to_pktgen
-    trex
-    trex_known_issue
-    usage_of_create_eal_and_start_testpmd
-    support_igb_uio
+    quick_start
+    usr_guide/index
diff --git a/doc/dts_gsg/intro.rst b/doc/dts_gsg/intro.rst
deleted file mode 100644
index e8753a0..0000000
--- a/doc/dts_gsg/intro.rst
+++ /dev/null
@@ -1,139 +0,0 @@
-Introduction
-============
-
-This document describes how to install and configure the Data Plane Development Kit Test Suite (DPDK Test Suite) in a Linux environment. Users can refer this document to enable this test infrastructure in their environment and don’t need go deeply with too much details about this framework.
-DPDK Test Suite is an automation test tool for DPDK software, a python-base library.  It can run on the tester machine, and communicate/manage DUT by SSH connection. DTF supports different kind of traffic generators, including DPDK-based PacketGen, third-party professional tester equipment (IXIA®).
-Data Plane Development Kit Test Suite (DPDK Test Suite) includes one set of test cases and DPDK generic test framework. DPDK Test Suite provides test example, references and framework for open source community. Based on DPDK Test Suite, everyone can develop their test plan, automation script and configuration for own features and platform. In addition, DPDK Test Suite provides a solution to allow that DPDK developers contribute their function test to certify their patch integration. It only requires limited effort to maintain test cases once merged into DPDK Test Suite.  Everyone can utilize DPDK Test Suite to measure performance and functionality for features.
-
-Please see DPDK Test Suite architecture in the following figures: 
-
-.. figure:: image/dts_soft_arch.png
-
-As generic test framework, DPDK Test Suite provides the following functions:
-
-*   Able to work with DUT (Device Under Test), which installed Fedora, Ubuntu, WindRiver, FreeBSD, RedHat and SUSE.
-*   Support virtualization hypervisors like Xen and Qemu.
-*   Support both software and hardware traffic generators, including Scapy, DPDK-based PacketGen and IXIA traffic generator, even third party packet generator via TCL or Python library.
-*   Provide configure files to customize test suite and test cases to run under DUT.
-*   Provide debug and log functionalities for tracking test cases execution process.
-*   Support to output test result by excel, log text file, etc.
-*   DPDK Test Suite provides one set of basic library to manage tester, DUT, test case, exception, generate report, and configure test plan by user configure files. It’s easy to develop user-defined test suite and test plan by self, and these test cases are able to integrate into DPDK Test Suite.
-*   With this test framework, user can automatically identify network topology, and easy to configure/deploy environment for DUT and tester, and provides flexibility to scale test capability by configuration.
-
-DPDK Test Suite environment includes DUT (Device under Test), Tester and packet generator. DPDK software will deployed and run on DUT. DPDK Test Suite should run on the Tester.
-
-Please see architecture in the following figures:
-
-
-.. figure:: image/dts_network_arch.png
-
-This architecture provides automatically mechanism to manage tester, DUT and packet generators, and remove dependency between test script and test environment/hardware. It defines one abstraction layer for DPDK Test Suite, and provides extensibility to add more test script.  
-In the DPDK Test Suite Test Framework, it provides the following modules to help to manage device, platform, configure and test results.
-
-.. table::
-
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | File Name             | Description                                                                                                                                                  |
-    +=======================+==============================================================================================================================================================+
-    | dts.py                | Main Application for DPDK Test Suite                                                                                                                         |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | main.py               | Test script to parse input parameter                                                                                                                         |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | dut.py                | Setup device under test including tool chain, IP address                                                                                                     |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | tester.py             | Provide API to setup tester environment including IP, port, etc.                                                                                             |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | project_dpdk.py       | Provide running environment for DPDK.                                                                                                                        |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | exception.py          | Manage User-defined exceptions used across the framework                                                                                                     |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | test_cases.py         | Provide a base class for creating DPDK Test Suite test cases                                                                                                 |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | logger.py             | Deal with different log files to record event or message                                                                                                     |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | serializer.py         | Provide wrapper class to manage temporary variables during execution                                                                                         |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | settings.py           | Setting for default network card and its identifiers supported by the framework                                                                              |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | utils.py              | Provide shared simple functions like IP address conversion and mask creation                                                                                 |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | ssh_connection.py     | Create session to host, implement send_expect and copy function                                                                                              |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | ssh_pexpect.py        | Handle ssh sessions between tester and DUT, Implement send_expect function to send command and get output data, Also support transfer files to tester or DUT |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | pmd_output.py         | Module for get all statics value by port in testpmd                                                                                                          |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | rst.py                | Generate Rst Test Result Report                                                                                                                              |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | stats_reporter.py     | Simple text file statistics generator                                                                                                                        |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | test_result.py        | Generic result container. Useful to store/retrieve results during a DTF execution                                                                            |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | excel_reporter.py     | Excel spreadsheet generator                                                                                                                                  |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | plotgraph.py          | Generate graphs for each test suite                                                                                                                          |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | plotting.py           | Generate Plots for performance test results                                                                                                                  |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | etgen.py              | Software packet generator                                                                                                                                    |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | ixia_buffer_parser.py | Helper class that parses a list of files containing IXIA captured frames extracting a sequential number on them                                              |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | ixiaDCB.tcl           | Third party Library which provided by IXIA, used to configure IXIA tester                                                                                    |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | ixiaPing6.tcl         | Third party Library which provided by IXIA, used to ping IXIA tester                                                                                         |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | IxiaWish.tcl          | Third party Library which provided by IXIA, set up TCL environment to use correct multiversion-compatible applications                                       |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | texttable.py          | Third party Library , create simple ASCII tables                                                                                                             |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | qemu_kvm.py           | Provide functionality for management and monitoring QEMU hypervisor                                                                                          |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | qemu_libvirt.py       | Provide functionality for usage of libvirt library                                                                                                           |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | virt_base.py          | Base class for virtual machine, supply basic management functions                                                                                            |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | virt_dut.py           | Generate instance for virtual machine, usage model is like DUT                                                                                               |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | virt_resource.py      | Provide resource management for virtual machine                                                                                                              |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | virt_scene.py         | Generate virtualization scenario based on configuration file                                                                                                 |
-    +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
-
-Beside Framework tool, DPDK Test Suite also defines one set of test cases. It includes basic test suite to verify basic functionality of DPDK library. These test script provides example and reference. Everyone can develop their test cases, verify their features functionality, and commit generic test report to maintainer. However, user-defined test cases, test plans and scripts must follow DPDK Test Suite standard including code standard, naming conventions, configure format, rst test plan, API.
-
-Please see test cases, which are included in the DPDK compliance test suites:
-
-.. table::
-
-    +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | Test Suite          | Descriptions                                                                                                                                                                                                 |
-    +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ 
-    | Command line        | Define a demo example of command line interface in RTE                                                                                                                                                       |
-    +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | hello_world         | Print a ``helloworld`` message on every enabled logic core.                                                                                                                                                  |
-    +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | Multi process       | Demonstrates the basics of sharing information between DPDK processes.                                                                                                                                       |
-    +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | Timer               | Shows how timer can be used in a RTE application.                                                                                                                                                            |
-    +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | Blocklist/AllowList | Tests Allowlist/Blocklist Features by Poll Mode Drivers.                                                                                                                                                     |
-    +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | checksum_offload    | Tests RX/TX L3/L4 Checksum offload features by Poll Mode Drivers                                                                                                                                             |
-    +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | jumbo_frame         | Tests jumbo frames features by Poll Mode Drivers                                                                                                                                                             |
-    +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | testpmd             | Provides benchmark tests for the Intel Ethernet Controller (Niantic) Poll Mode Driver.                                                                                                                       |
-    +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | l2fwd               | Provides a basic packet processing application using DPDK. It is a layer-2 (L2) forwarding application which takes traffic from a single RX port and transmits it with few modification on a single TX port. |
-    +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | L3fwd               | Verifies Layer-3 Forwarding results using ``l3fwd`` application.                                                                                                                                             |
-    +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | IP fragment         | Verifies IPv4 fragmentation using ``ipv4_frag`` application.                                                                                                                                                 |
-    +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | Flow direction      | Verifies  the Flow Director feature of the Intel 82599 10GbE Ethernet Controller                                                                                                                             |
-    +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | link_flowctrl       | Verifies  Ethernet Link Flow Control Features by Poll Mode Drivers                                                                                                                                           |
-    +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-    | ieee1588            | Tests the IEEE1588 Precise Time Protocol offload supported in Poll Mode Drivers.                                                                                                                             |
-    +---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
diff --git a/doc/dts_gsg/migrate_from_etgen_to_pktgen.rst b/doc/dts_gsg/migrate_from_etgen_to_pktgen.rst
deleted file mode 100644
index e08d00b..0000000
--- a/doc/dts_gsg/migrate_from_etgen_to_pktgen.rst
+++ /dev/null
@@ -1,229 +0,0 @@
-
-======================
-Etgen to Pktgen Guides
-======================
-
-If you are working on etgen, and this document can help you to update your
-test suites to pktgen rapidly. Etgen is not under maitenance, and it will
-be removed from DTS some days.
-
-pktgen usage please refer to doc `pktgen_prog_guide <pktgen_prog_guide.html>`__.
-
-import new class
-----------------
-
-#. import a new module:
-
-.. code-block:: python
-
-   from pktgen import PacketGeneratorHelper
-
-initialize an instance in `def set_up_all(self)`
-------------------------------------------------
-
-.. code-block:: python
-
-   def set_up_all(self):
-   ...
-      self.pktgen_helper = PacketGeneratorHelper()
-
-create streams for pktgen instance
-----------------------------------
-each pcap file should only contain one packet.
-
-.. code-block:: python
-
-   pcap1 = os.sep.join([self.pktgen.output_path, "{0}.pcap".format(port)])
-   flow1 = "Ether()/IP()/UDP()/("X")"
-   self.tester.scapy_append('wrpcap("%s", [flow])' % (pcap1, flow1))
-   self.tester.scapy_execute()
-
-   pcap2 = os.sep.join([self.pktgen.output_path, "{0}.pcap".format(port)])
-   flow2 = "Ether()/IP()/UDP()/("X")"
-   self.tester.scapy_append('wrpcap("%s", [flow])' % (pcap2, flow2))
-   self.tester.scapy_execute()
-
-   tgen_input = []
-   tgen_input.append([tx_port, rx_port, pcap1])
-   tgen_input.append([tx_port, rx_port, pcap2])
-
-pcap field variable(optional)
------------------------------
-If no protocol layer field vary requirement, ignore this content.
-
-field key definition
-~~~~~~~~~~~~~~~~~~~~
-
-#. ip protocol layer:
-
-.. code-block:: python
-
-   # protocol layer name
-   'mac':  {
-      # field name
-      'src': {
-         # field value vary range
-         'range': 64,
-         # field value vary step
-         'step': 1,
-         # action: inc/dec/random
-         'action': 'inc'},
-      'dst': {'range': 64, 'step': 1, 'action': 'inc'},
-       }
-
-#. mac protocol layer:
-
-.. code-block:: python
-
-   # protocol layer name
-   'mac':  {
-      # field name
-      'src': {
-         # field value vary range
-         'range': 64,
-         # field value vary step
-         'step': 1,
-         # action: inc/dec/random
-         'action': 'inc'},
-      'dst': {'range': 64, 'step': 1, 'action': 'inc'},
-       }
-
-#. vlan protocol layer:
-
-.. code-block:: python
-
-   # protocol layer name
-   'vlan':  {
-      '0': {
-         # field value vary range
-         'range': 64,
-         # field value vary step
-         'step': 1,
-         # action: inc/dec/random
-         'action': 'inc'},
-       }
-
-usage example
-~~~~~~~~~~~~~
-
-.. code-block:: python
-
-   def set_up_all(self):
-      ...
-      self.pktgen_helper = PacketGeneratorHelper()
-      ...
-
-   def set_fields(self):
-      fields_config = {
-         'ip':  {
-            'src': {'range': 64, 'action': 'inc'},
-            'dst': {'action': 'random'}},}
-      return fields_config
-
-   def test_perf_xxxx(self):
-      ...
-      vm_config= self.set_fields() # optional
-      # clear streams before add new streams
-      self.tester.pktgen.clear_streams()
-      # run packet generator
-      ratePercent = 100
-      streams = self.pktgen_helper.prepare_stream_from_tginput(
-                         tgenInput, ratePercent, vm_config, self.tester.pktgen)
-      _, pps = self.tester.pktgen.measure_throughput(stream_ids=streams)
-      ...
-
-change etgen interface to pktgen interface
-------------------------------------------
-pktgen interface use the same input parameter/return value definition as
-etgen interface.
-
-throughput
-~~~~~~~~~~
-
-etgen:
-
-.. code-block:: python
-
-   self.tester.traffic_generator_throughput(tgen_input)
-
-pktgen:
-
-.. code-block:: python
-
-   vm_config= self.set_fields() # optional
-   # clear streams before add new streams
-   self.tester.pktgen.clear_streams()
-   # run packet generator
-   ratePercent = 100
-   streams = self.pktgen_helper.prepare_stream_from_tginput(
-                        tgenInput, ratePercent, vm_config, self.tester.pktgen)
-   _, pps = self.tester.pktgen.measure_throughput(stream_ids=streams)
-
-loss
-~~~~
-
-etgen:
-
-.. code-block:: python
-
-   self.tester.traffic_generator_loss(tgen_input)
-
-pktgen:
-
-.. code-block:: python
-
-   vm_config= self.set_fields() # optional
-   # clear streams before add new streams
-   self.tester.pktgen.clear_streams()
-   # run packet generator
-   ratePercent = 100
-   streams = self.pktgen_helper.prepare_stream_from_tginput(
-                              tgenInput, ratePercent, vm_config, self.tester.pktgen)
-   result = self.tester.pktgen.measure_loss(stream_ids=streams)
-
-latency
-~~~~~~~
-
-etgen:
-
-.. code-block:: python
-
-   self.tester.traffic_generator_latency(tgen_input)
-
-pktgen:
-
-.. code-block:: python
-
-   vm_config= self.set_fields() # optional
-   # clear streams before add new streams
-   self.tester.pktgen.clear_streams()
-   # run packet generator
-   ratePercent = 100
-   streams = self.pktgen_helper.prepare_stream_from_tginput(
-                        tgenInput, ratePercent, vm_config, self.tester.pktgen)
-   latencys = self.tester.pktgen.measure_latency(stream_ids=streams)
-
-rfc2544
-~~~~~~~
-
-etgen:
-
-.. code-block:: python
-
-   self.tester.run_rfc2544(tgen_input)
-
-pktgen:
-
-.. code-block:: python
-
-   vm_config= self.set_fields() # optional
-   # clear streams before add new streams
-   self.tester.pktgen.clear_streams()
-   # run packet generator
-   ratePercent = 100
-   streams = self.pktgen_helper.prepare_stream_from_tginput(
-                        tgenInput, ratePercent, vm_config, self.tester.pktgen)
-   # set traffic option
-   traffic_opt = {'pdr': 0.01, 'duration': 5}
-   zero_loss_rate, tx_pkts, rx_pkts = \
-     self.tester.pktgen.measure_rfc2544(stream_ids=streams, options=traffic_opt)
diff --git a/doc/dts_gsg/multiple_vm.rst b/doc/dts_gsg/multiple_vm.rst
deleted file mode 100644
index 07dd44f..0000000
--- a/doc/dts_gsg/multiple_vm.rst
+++ /dev/null
@@ -1,87 +0,0 @@
-Multiple Virtual Machines Management
-====================================
-
-When managing multiple virtual machines, waiting around 2 minutes for each VM will be exhausted. So DTS imported parallel threads model into multiple VMs management scenario.
-
-.. note::
-    Critical resources and actions which can't be handled in parallel have been protected by function level lock.
-
-Command arguments
------------------
-
-Multiple VMs module support start VMs or send commands to VMs in parallel with specified arguments format.
-
-Arguments for "start" command:
-
-.. table::
-
-    +-----------------+----------------------------------+----------------+-------------+
-    | name            | Description                      | Default value  | Must have   |
-    |                 |                                  |                |             |
-    +-----------------+----------------------------------+----------------+-------------+
-    | name            | virtual machine name             | N/A            | Yes         |
-    +-----------------+----------------------------------+----------------+-------------+
-    | dut_id          | index of DUT                     | 0              | No          |
-    +-----------------+----------------------------------+----------------+-------------+
-    | autodetect_topo | whether detect network topology  | False          | No          |
-    |                 | automatically                    |                |             |
-    +-----------------+----------------------------------+----------------+-------------+
-    | virt_config     | virtual machine config location  | N/A            | Alternative |
-    +-----------------+----------------------------------+----------------+-------------+
-    | virt_params     | local parameters of virtual      | N/A            | Alternative |
-    |                 | machine                          |                |             |
-    +-----------------+----------------------------------+----------------+-------------+
-
-Arguments for "cmd" command:
-
-.. table::
-
-    +-----------------+----------------------------------+----------------+-------------+
-    | name            | Description                      | Default value  | Must have   |
-    |                 |                                  |                |             |
-    +-----------------+----------------------------------+----------------+-------------+
-    | name            | virtual machine name             | N/A            | Yes         |
-    +-----------------+----------------------------------+----------------+-------------+
-    | dut_id          | index of DUT                     | 0              | No          |
-    +-----------------+----------------------------------+----------------+-------------+
-    | commands        | list of commands which will be   | N/A            | Yes         |
-    |                 | sent into the vitual machine     |                |             |
-    +-----------------+----------------------------------+----------------+-------------+
-    | expects         | list of expect output of the     | N/A            | Yes         |
-    |                 | commands                         |                |             |
-    +-----------------+----------------------------------+----------------+-------------+
-    | timeouts        | list of timeout value of the     | N/A            | Yes         |
-    |                 | commands                         |                |             |
-    +-----------------+----------------------------------+----------------+-------------+
-
-.. note::
-    If there's nothing expected for the command, still need to define expected string as blank
-
-Multiple module will catagorize and save the result value after all tasks have been done. Later users can retrieve the result by function get_parallel_result.
-
-Sample Code
------------
-
-.. code-block:: console
-
-    vm_task = MultipleVM(max_vm=self.VM_NUM, duts=self.duts)
-
-    for dut_id in range(len(self.duts)):
-        for vm_idx in range(VM_NUM):
-            vm_name = "vm%d" % vm_idx
-            args = {'name': vm_name,
-                    'dut_id': dut_id,
-                    'autodetect_topo': False,
-                    'virt_params': {
-                        'qemu': [{'path': '/usr/local/bin/qemu-system-x86_64'}],
-                        'cpu': [{'model': 'host', 'number': '1', 'cpupin': ''}],
-                        'mem': [{'size': '1024', 'hugepage': 'yes'}],
-                        'disk': [{'file': '/storage/vm-image/%s.qcow2' % vm_name}],
-                        'login': [{'user': 'root', 'password': 'root'}],
-                        'device': None}
-                    }
-
-            vm_task.add_parallel_task(action="start", config=args)
-
-    vm_task.do_parallel_task()
-    print vm_task.get_parallel_result()
diff --git a/doc/dts_gsg/pktgen_prog_guide.rst b/doc/dts_gsg/pktgen_prog_guide.rst
deleted file mode 100644
index 26ba56a..0000000
--- a/doc/dts_gsg/pktgen_prog_guide.rst
+++ /dev/null
@@ -1,584 +0,0 @@
-
-===================
-Pktgen How-to Guide
-===================
-
-The old module *etgen* is only support hardward packet generator `Ixia Explorer`
-which is not friendly for users to get. So DTS community refined DTS framework to
-support another software packet generator `Trex` which is an open source project,
-and user can get it easily.
-
-these definition and usage pattern come from doc `pktgen-API-1.1.docx` and etgen
-usage in dts. For trex(CISCO) rapid iterative development speed, we lack of
-adequate manpower to keep up with it. Here we recommend to use trex v2.41/v2.42/v2.43
-to run pktgen/trex.
-
-add stream
-==========
-add stream in pktgen streams table.
-
-one stream content including::
-
-   tx_port: transmit port idx in tester.ports_info.
-   rx_port: receive port idx in tester.ports_info.
-   pcap: pcap file or Packet instance, Only support one packet in it.
-
-.. code-block:: python
-
-   tx_port = self.tester.get_local_port(dut_port_index1)
-   rx_port = self.tester.get_local_port(dut_port_index2)
-
-   stream_id = hPktgen.add_stream(tx_port, rx_port, pcap)
-
-config stream
-=============
-configure a stream option.
-
-definition
-----------
-Currently pktgen support ethernet/ipv4/vlan protocol layer some field vary with
-increase/decrease/random value.
-
-stream option contain::
-
-   'pcap': network packet format
-   'fields_config': protocol layer field behavior(optional)
-   'stream_config': stream transmit behavior
-   'flow_control': port flow control(optional)
-
-pcap
-++++
-It is a network packet format. It can be a absolute path of pcap file or
-an instance of scapy Packet. It should only contain one packet format.
-
-.. code-block:: python
-
-   Example 1:
-
-      pcap = <Ether  dst=FF:FF:FF:FF:FF:FF src=00:00:00:00:00:00 type=IPv4 |<IP  frag=0 proto=udp src=0.0.0.1 dst=0.0.0.255 |<UDP  sport=22 dport=50 |<Raw  load='xxxxxxxxxxxxxxxxxx' |>>>>
-
-   Example 2:
-
-      pcap = "/root/xxx.pcap"
-
-field option
-++++++++++++
-define every layer's field behavior.
-
-'mac'
-`````
-'mac' is ethernet protocol layer name.
-
-.. code-block:: python
-
-   # field name
-   'src': {
-      # action: inc/dec/random
-      'action':'inc',
-      # field end value should be bigger than field start value
-      'end':   '00:00:00:00:00:FF',
-      # field start value
-      'start': '00:00:00:00:00:02',
-      # field value vary step
-      'step': 1},
-   'dst': {
-      # action: inc/dec/random
-      'action':'inc',
-      # field end value should be bigger than field start value
-      'end':   'ff:00:00:00:00:FF',
-      # field start value
-      'start': 'ff:00:00:00:00:02',
-      # field value vary step
-      'step': 1},
-
-'ip'
-````
-'ip' is ip protocol layer name.
-
-.. code-block:: python
-
-   # field name
-   'src': {
-      # action: inc/dec/random
-      'action': 'inc',
-      # field end value should be bigger than field start value
-      'end':   '16.0.0.16',
-      # field start value
-      'start': '16.0.0.1',
-      # field value vary step
-      'step': 1},
-   # field name
-   'dst': {
-      # action: inc/dec/random
-      'action': 'inc',
-      # field end value should be bigger than field start value
-      'end':   '48.0.0.255',
-      # field start value
-      'start': '48.0.0.1',
-      # field value vary step
-      'step': 1},
-
-'vlan'
-``````
-'vlan' is vlan protocol layer name.
-
-.. code-block:: python
-
-   # internal vlan
-   0: {
-      # action: inc/dec/random
-      'action': 'inc',
-      # field end value should be bigger than field start value
-      'end': 52,
-      # field start value
-      'start': 50,
-      # field value vary step
-      'step': 1},
-   # external vlan
-   1: {
-      # action: inc/dec/random
-      'action': 'inc',
-      # field end value should be bigger than field start value
-      'end': 52,
-      # field start value
-      'start': 50,
-      # field value vary step
-      'step': 1},
-
-'stream_config'
-+++++++++++++++
-define a stream transmit behavior.
-
-basic content including::
-
-   'rate':  0 ~ 100 int type, port line rate should set it.
-   'transmit_mode': TRANSMIT_CONT/TRANSMIT_S_BURST
-       TRANSMIT_CONT define a continuous transmit.
-       TRANSMIT_S_BURST define a burst transmit with custom number of packets.
-
-.. code-block:: python
-
-   from pktgen_base import TRANSMIT_CONT, TRANSMIT_S_BURST
-
-   stream_config = {
-       'rate': 100,
-       # TRANSMIT_CONT define a continuous transmit.
-       # TRANSMIT_S_BURST define a burst transmit with custom number of packets.
-       'transmit_mode': TRANSMIT_CONT
-   }
-
-stream option examples
-----------------------
-
-normal stream option
-++++++++++++++++++++
-normal stream ignore `fields_config` configuration option.
-
-.. code-block:: python
-
-   Example 1:
-      option = {
-         'pcap': "/root/xxx.pcap",
-         'stream_config': {
-             'rate': 100,
-             'transmit_mode': TRANSMIT_CONT}}
-
-   Example 2:
-      option = {
-         'pcap': <Ether  dst=00:00:00:00:20:00 src=00:00:00:00:00:FF type=IPv4 |<IP  frag=0 proto=udp src=0.0.0.1 dst=0.0.0.255 |<UDP  sport=22 dport=50 |<Raw  load='xxxxxxxxxxxxxxxxxx' |>>>>,
-         'stream_config': {
-             'rate': 100,
-             'transmit_mode': TRANSMIT_CONT}}
-
-stream option with mac increase/decrease/random
-+++++++++++++++++++++++++++++++++++++++++++++++
-
-.. code-block:: python
-
-   action = 'inc' or 'dec' or 'random'
-   option = {
-      'pcap': "/root/xxx.pcap",
-      'fields_config': {
-         'mac': {
-            'dst': {
-               'action': action,
-               'end':   '00:00:00:00:20:00',
-               'start': '00:00:00:00:00:FF',
-               'step': 1},
-            'src': {
-               'action': action,
-               'end':   '00:00:00:00:00:FF',
-               'start': '00:00:00:00:00:02',
-               'step': 1}}},
-      'stream_config': {
-            'rate': 100,
-            'transmit_mode': TRANSMIT_CONT
-            }
-        }
-
-stream option with ip increase/decrease/random
-++++++++++++++++++++++++++++++++++++++++++++++
-
-.. code-block:: python
-
-   action = 'inc' or 'dec' or 'random'
-   option = {
-         'pcap': "/root/xxx.pcap",
-         'fields_config': {
-            'ip': {
-               'dst': {
-                  'action': action,
-                  'end':   '48.0.0.255',
-                  'start': '48.0.0.1',
-                  'step': 1},
-               'src': {
-                  'action': action,
-                  'end':   '16.0.0.16',
-                  'start': '16.0.0.1',
-                  'step': 1}}},
-         'stream_config': {
-             'rate': 100,
-             'transmit_mode': TRANSMIT_CONT,
-             }
-         }
-
-stream option with vlan increase/decrease/random
-++++++++++++++++++++++++++++++++++++++++++++++++
-
-.. code-block:: python
-
-   action = 'inc' or 'dec' or 'random'
-   option = {
-         'pcap': "/root/xxx.pcap",
-         'fields_config': {
-            'ip': {
-               0: {
-                  'action': action,
-                  'end':   55,
-                  'start': 50,
-                  'step':  1},
-         'stream_config': {
-             'rate': 100,
-             'transmit_mode': TRANSMIT_CONT,
-             }
-         }
-
-burst stream option
-+++++++++++++++++++
-
-.. code-block:: python
-
-   option = {
-         'pcap': "/root/xxx.pcap",
-         'stream_config': {
-             'rate': 100,
-             # set stream transmit mode
-             'transmit_mode': TRANSMIT_S_BURST,
-             'txmode' : {
-                # total packets
-                'total_pkts': 1000},
-             }
-         }
-
-stream option with flow control
-+++++++++++++++++++++++++++++++
-flow control open (trex not supported)
-
-.. code-block:: python
-
-   option = {
-      'flow_control': {
-            # 0: disable flow control
-            # 1: enable flow control
-           'flag': 1},
-      'pcap': "/root/xxx.pcap",
-      'stream_config': {
-          'rate': 100,
-          'transmit_mode': TRANSMIT_CONT}}
-
-measure
-=======
-pktgen measure_xxxx return value is the same as etgen, `measure_xxxx` and
-`measure` are both supported. If traffic option is not set, use default values.
-
-two usage examples of pktgen measure method
--------------------------------------------
-
-.. code-block:: python
-
-   Example 1:
-
-      from pktgen import getPacketGenerator, PKTGEN_TREX
-
-      hPktgen = getPacketGenerator(tester, PKTGEN_TREX)
-
-      traffic_option = {'rate': 100}
-      hPktgen.measure_throughput(stream_ids, traffic_opt)
-
-   Example 2:
-
-      from pktgen import getPacketGenerator, PKTGEN_TREX
-
-      hPktgen = getPacketGenerator(tester, PKTGEN_TREX)
-
-      traffic_option = {
-         'method': 'throughput',
-         'rate': 100
-      }
-      hPktgen.measure(stream_ids, traffic_opt)
-
-throughput
-----------
-throughput testing scenario.
-
-option
-++++++
-.. code-block:: python
-
-   traffic_option = {
-      # test method name, if use `measure_throughput`, ignore this key
-      'method': 'throughput',
-      # port rate percent, float(0--100), default value is 100.(reserved)
-      'rate': 100,
-      # warm up time before start main transmission. If it is set, it will start
-      # a custom time transmission to make sure packet generator under good
-      # status. It is an optional key.
-      'delay': 5,
-      # the interval time of get throughput statistic (second).
-      # If set this key value, pktgen will return several throughput statistic
-      # data in a duration. If not set this key value, only return one statistic
-      # data. It is used coupled with `duration` option.
-      'interval': 1,
-      # this key works with ``interval`` key. If it is set, the callback
-      # of suite level will be executed after getting throughput statistic.
-      # callback method should define as below, don't add sleep in this method.
-      'callback' : callback_method,
-      # transmission lasting time(second), default value is 10 second.
-      'duration': 5}
-
-return value
-++++++++++++
-bps_rx_total: Received bits per second
-pps_rx_total: Received packets per second
-
-.. code-block:: python
-
-   return_value = (bps_rx_total, pps_rx_total)
-
-loss
-----
-loss rate testing scenario.
-
-option
-++++++
-
-.. code-block:: python
-
-   traffic_option = {
-      # test method name, if use `measure_loss`, ignore this key
-      'method': 'loss',
-      # port rate percent, float(0--100), default value is 100.(reserved)
-      'rate': 100,
-      # warm up time before start main transmission. If it is set, it will start
-      # a custom time transmission to make sure packet generator under good
-      # status. It is an optional key.
-      'delay': 5,
-      # transmission lasting time(second), default value is 10 second.
-      'duration': 5}
-
-return value
-++++++++++++
-
-.. code-block:: python
-
-   loss_stats = (loss_rate, tx_pkts, rx_pkts)
-
-latency
--------
-latency testing scenario.
-
-option
-++++++
-
-.. code-block:: python
-
-   traffic_option = {
-      # test method name, if use `measure_latency`, ignore this key
-      'method': 'latency',
-      # port rate percent, float(0--100), default value is 100.(reserved)
-      'rate': 100,
-      # warm up time before start main transmission. If it is set, it will start
-      # a custom time transmission to make sure packet generator under ready
-      # status. It is an optional key.
-      'delay': 5,
-      # transmission lasting time(second), default value is 10 second.
-      'duration': 5}
-
-return value
-++++++++++++
-
-.. code-block:: python
-
-   latency_stats = { 'min':     15,
-                     'max':     15,
-                     'average': 15,}
-
-rfc2544 option
---------------
-rfc2544 testing scenario by decreasing step.
-
-option
-++++++
-
-.. code-block:: python
-
-   traffic_option = {
-      # test method name, if use `measure_rfc2544`, ignore this key.
-      'method': 'rfc2544',
-      # port rate percent at first round testing, 0 ~ 100, default is 100.
-      'rate': 100,
-      # permit packet drop rate, default is 0.001.
-      'pdr': 0.001,
-      # port rate percent drop step, 0 ~ 100 , default is 1.
-      'drop_step': 1,
-      # warm up time before start main transmission. If it is set, it will start
-      # a custom time transmission to make sure packet generator under ready
-      # status. It is an optional key.
-      'delay': 5,
-      # transmission lasting time(second), default value is 10 second.
-      'duration': 5}
-
-return value
-++++++++++++
-
-.. code-block:: python
-
-   loss_stats = (loss_rate, tx_pkts, rx_pkts)
-
-rfc2544_dichotomy option
-------------------------
-rfc2544 testing scenario using dichotomy algorithm.
-
-option
-++++++
-
-.. code-block:: python
-
-   traffic_option = {
-      # test method name, if use `measure_rfc2544_dichotomy` method, ignore this key.
-      'method': 'rfc2544_dichotomy',
-      # dichotomy algorithm lower bound rate percent, default is 0.
-      'min_rate': 0,
-      # dichotomy algorithm upper bound rate percent, default is 100.
-      'max_rate': 100,
-      # dichotomy algorithm accuracy, default 0.001.
-      'accuracy': 0.001,
-      # permit packet drop rate, default is 0.001.
-      'pdr': 0.001,
-      # warm up time before start main transmission. If it is set, it will start
-      # a custom time transmission to make sure packet generator under ready
-      # status. It is an optional key.
-      'delay': 5,
-      # transmission lasting time(second), default value is 10 second.
-      'duration': 10}
-
-return value
-++++++++++++
-
-.. code-block:: python
-
-   loss_stats = (loss_rate, tx_pkts, rx_pkts)
-
-
-reference example
-=================
-This example show how to use pktgen in suite script. In fact, most scenario are
-more simpler than this. Part of code is pseudo code and it can't be ran directly.
-
-testing scenario::
-
-   create four streams on two links, each link attach two streams. On one link,
-   one stream set mac src increase and packet format is a pcap file, the other
-   stream set ip src random / dst decrease and packet format is a scapy Packet
-   instance. All streams use continuous transmit and run rfc2544 scenario using
-   trex packet generator.
-
-.. code-block:: python
-
-   # import pktgen lib
-   from pktgen import getPacketGenerator, PKTGEN_TREX, TRANSMIT_CONT
-
-   # create a pktgen instance
-   hPktgen = getPacketGenerator(tester, PKTGEN_TREX)
-
-   # create packet
-   pcap1 = <Ether  dst=FF:FF:FF:FF:FF:FF src=00:00:00:00:00:00 type=IPv4 |<IP  frag=0 proto=udp src=0.0.0.1 dst=0.0.0.255 |<UDP  sport=22 dport=50 |<Raw  load='xxxxxxxxxxxxxxxxxx' |>>>>
-   pcap2 = "/root/xxx.pcap"
-
-   # attach stream to pktgen
-   stream_ids = []
-   tx_port1 = self.tester.get_local_port(dut_port_index1)
-   rx_port1 = self.tester.get_local_port(dut_port_index2)
-   stream_id_1 = hPktgen.add_stream(tx_port1, rx_port1, pcap1)
-   stream_id_2 = hPktgen.add_stream(tx_port1, rx_port1, pcap2)
-   stream_ids.append(stream_id_1)
-   stream_ids.append(stream_id_2)
-
-   tx_port2 = self.tester.get_local_port(dut_port_index2)
-   rx_port2 = self.tester.get_local_port(dut_port_index1)
-   stream_id_3 = hPktgen.add_stream(tx_port2, rx_port2, pcap1)
-   stream_id_4 = hPktgen.add_stream(tx_port2, rx_port2, pcap2)
-   stream_ids.append(stream_id_3)
-   stream_ids.append(stream_id_4)
-
-   # set pcap1 with mac protocol layer field vary configuration
-   stream_option1 = {
-      'pcap': pcap1,
-      'fields_config': {
-         'mac': {
-            'src': {
-               'action': 'inc',
-               'end':   '00:00:00:00:00:FF',
-               'start': '00:00:00:00:00:00',
-               'step': 1}}},
-        'stream_config': {
-            'rate': 100,
-            'transmit_mode': TRANSMIT_CONT
-            }
-        }
-   # set stream option
-   hPktgen.config_stream(stream_id_1, stream_option1)
-   hPktgen.config_stream(stream_id_3, stream_option1)
-
-   # set pcap2 with ip protocol layer field vary configuration
-   stream_option2 = {
-      'pcap': pcap2,
-      'fields_config': {
-         'ip': {
-            'dst': {
-               'action': 'dec',
-               'end':   '0.0.0.255',
-               'start': '0.0.0.1',
-               'step': 1},
-            'src': {
-               'action': 'random',
-               'end':   '0.0.0.64',
-               'start': '0.0.0.1',
-               'step': 1}}},
-        'stream_config': {
-            'rate': 100,
-            'transmit_mode': TRANSMIT_CONT
-            }
-        }
-   # set stream option
-   hPktgen.config_stream(stream_id_2, stream_option2)
-   hPktgen.config_stream(stream_id_4, stream_option2)
-
-   # run testing scenario
-   traffic_option = {
-      'method':    'rfc2544',
-      'rate':      100,
-      'pdr':       0.001,
-      'drop_step': 1}
-
-   hPktgen.measure(stream_ids, traffic_opt)
diff --git a/doc/dts_gsg/quick_start.rst b/doc/dts_gsg/quick_start.rst
new file mode 100644
index 0000000..b26cf26
--- /dev/null
+++ b/doc/dts_gsg/quick_start.rst
@@ -0,0 +1,310 @@
+=================
+Quick start guide
+=================
+
+Introduction
+============
+
+This document describes how to install and configure the Data Plane Development Kit Test Suite (DTS) in a Linux environment.
+It is designed to get user to set up DTS quickly in their environment without going deeply into detail.
+
+DTS can run on a tester machine or a DUT machine or the third machine to communicate/manage tester/DUT by SSH connection.
+DTS supports different kinds of traffic generators, including Scapy, TRex, IXIA.
+The example set up DTS on as tester machine, and use Scapy as traffic generator to run functional testing.
+
+System Requirements
+===================
+
+This chapter describes the packages required to set up DTS.
+For the DPDK requirements, please consult `Data Plane Development Kit Getting Started Guide <http://dpdk.org/doc/guides>`_.
+
+Hardware Recommendation
+-----------------------
+
+Our regression setups uses Intel x86 platforms with mainstream Intel ethernet cards.
+The following platforms have been tested and are recommended.
+
+.. |reg|    unicode:: U+000AE .. REGISTERED SIGN
+.. |trade|    unicode:: U+2122 .. TRADE MARK SIGN
+
+* DTS and Tester system
+
+	* CPU
+		* Intel\ |reg| Xeon\ |reg| Platinum 8280M CPU @ 2.70GHz
+		* Intel\ |reg| Xeon\ |reg| Platinum 8180 CPU @ 2.50GHz
+		* Intel\ |reg| Xeon\ |reg| Gold 6252N CPU @ 2.30GHz
+
+	* OS
+		* Ubuntu 20.04
+		* Ubuntu 18.04
+
+* DUT system
+
+	* CPU
+
+		* Intel\ |reg| Atom\ |trade| CPU C3758 @ 2.20GHz
+		* Intel\ |reg| Atom\ |trade| CPU C3858 @ 2.00GHz
+		* Intel\ |reg| Atom\ |trade| CPU C3958 @ 2.00GHz
+		* Intel\ |reg| Xeon\ |reg| CPU D-1541 @ 2.10GHz
+		* Intel\ |reg| Xeon\ |reg| CPU D-1553N @ 2.30GHz
+		* Intel\ |reg| Xeon\ |reg| CPU E5-2680 0 @ 2.70GHz
+		* Intel\ |reg| Xeon\ |reg| CPU E5-2680 v2 @ 2.80GHz
+		* Intel\ |reg| Xeon\ |reg| CPU E5-2699 v3 @ 2.30GHz
+		* Intel\ |reg| Xeon\ |reg| CPU E5-2699 v4 @ 2.20GHz
+		* Intel\ |reg| Xeon\ |reg| Gold 5218N CPU @ 2.30GHz
+		* Intel\ |reg| Xeon\ |reg| Gold 6139 CPU @ 2.30GHz
+		* Intel\ |reg| Xeon\ |reg| Gold 6252N CPU @ 2.30GHz
+		* Intel\ |reg| Xeon\ |reg| Platinum 8180 CPU @ 2.50GHz
+		* Intel\ |reg| Xeon\ |reg| Platinum 8280M CPU @ 2.70GHz
+
+	* OS
+
+		* CentOS 8.3
+		* CentOS Stream 8
+		* Fedora 33
+		* Red Hat Enterprise Linux Server release 8.3
+		* Suse 15 SP2
+		* Ubuntu 20.04
+		* Ubuntu 20.10
+
+	* NICs
+
+	        * Intel\ |reg| Ethernet Controller E810-C for SFP (4x25G)
+	        * Intel\ |reg| Ethernet Controller E810-C for QSFP (2x100G)
+	        * Intel\ |reg| Ethernet Converged Network Adapter X710-DA4 (4x10G)
+	        * Intel\ |reg| Ethernet Converged Network Adapter XXV710-DA2 (2x25G)
+	        * Intel\ |reg| 82599ES 10 Gigabit Ethernet Controller
+
+Topology Example
+----------------
+
+2 Teseter interfaces connect to 2 DUT interfaces back to back.
+
+Dependencies
+------------
+
+SSH Service
+~~~~~~~~~~~
+
+Tester and DUT should have one interface connected to the same internet, so that they can be accessed by each other from local IP address
+
+.. code-block:: console
+
+   apt-get install sshd                # download / install ssh software
+   systemctl enable ssh                # start ssh service
+
+.. note::
+
+   Firewall should be disabled that all packets can be accepted by NIC interfaces.
+
+.. code-block:: console
+
+   systemctl disable firewalld.service
+
+Python modules for DTS & Tester
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The python dependences are recorded in requirements.txt.
+Please install them as the following:
+
+.. code-block:: console
+
+   apt-get install python3
+   python3 -m pip install requirements.txt
+
+BIOS setting for DUT
+~~~~~~~~~~~~~~~~~~~~
+
+DPDK prefer devices bound to ``vfio-pci`` kernel module, therefore, please enable VT-d and VT-x:
+
+.. code-block:: console
+
+   Advanced -> Integrated IO Configuration -> Intel(R) VT for Directed I/O <Enabled>
+   Advanced -> Processor Configuration -> Intel(R) Virtualization Technology <Enabled>
+
+DPDK running Prerequisite
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Recommend to use 1G Hugepage for DPDK running, add ``hugepagesz=1G hugepages=40 default_hugepagesz=1G`` in Linux cmdline.
+For more details, please refer to `Data Plane Development Kit Getting Started Guide <http://dpdk.org/doc/guides>`_.
+
+Running DTS
+===========
+
+Getting DTS Code
+----------------
+
+Get DTS code from remote repo.
+
+.. code-block:: console
+
+   [root@tester ~]#  git clone http://dpdk.org/git/tools/dts
+   [root@tester ~]#  ls dts
+   [root@tester dts]# conf CONTRIBUTING.TXT dep doc dts execution.cfg executions framework nics output requirements.txt test_plans tests tools version.py
+
+Preparing DPDK tarball
+----------------------
+
+DPDK source code should be packed as "dpdk.tar.gz" and moved into dts/dep:
+
+.. code-block:: console
+
+    tar -czvf dpdk.tar.gz dpdk
+    cp dpdk.tar.gz ~/dts/dep
+
+Configuring DTS
+---------------
+
+A few of files should be configured, including execution.cfg, conf/crbs, conf/ports.cfg.
+
+execution.cfg
+~~~~~~~~~~~~~
+
+.. code-block:: console
+
+   [Execution1]
+   crbs=192.168.1.1
+   drivername=vfio-pci
+   build_type=meson
+   test_suites=
+        hello_world,
+   targets=
+        x86_64-default-linuxapp-gcc,
+   parameters=nic_type=cfg:func=true
+
+* crbs: IP address of the DUT system
+* test_suites: a list of test suites to be executed
+
+conf/crbs.cfg
+~~~~~~~~~~~~~
+
+.. code-block:: console
+
+   [192.168.1.1]
+   dut_ip=192.168.1.1
+   dut_user=root
+   dut_passwd=dutpasswd
+   os=linux
+   tester_ip=192.168.1.2
+   tester_passwd=testerpasswd
+   channels=4
+   bypass_core0=True
+
+* dut_ip: IP address of the DUT system, same as crbs in execution.cfg
+* dut_user: User name of DUT linux account
+* dut_passwd: Password of DUT linux account
+* tester_ip: IP address of tester
+* tester_passwd: Password of Tester linux account, user name should same as dut_user
+
+conf/ports.cfg
+~~~~~~~~~~~~~~
+
+.. code-block:: console
+
+   [192.168.1.1]
+   ports =
+       pci=0000:06:00.0,peer=0000:81:00.0;
+       pci=0000:06:00.1,peer=0000:81:00.1;
+
+* [192.168.1.1]: same as crbs in execution.cfg and dut_ip in conf/crbs.cfg
+* pci: pci address of DUT port
+* peer: pci address of Tester port which connected to the DUT port whose pci is `pci`.
+
+The topology for the configuration is:
+
+.. code-block:: console
+
+   DUT port0 (0000:06:00.0) --- Tester port0 (0000:81:00.0)
+   DUT port0 (0000:06:00.1) --- Tester port0 (0000:81:00.1)
+
+Launch DTS
+----------
+
+As we have prepared the zipped dpdk file and configuration file, just type the followed command “./dts”, it will start the validation process.
+
+.. code-block:: console
+
+    [root@tester ~]# ./dts
+
+                           dts:
+    DUT 192.168.1.1
+                        tester: ssh root@192.168.1.2
+                        tester: ssh root@192.168.1.2
+                        tester: python3 -V
+                  tester_scapy: ssh root@192.168.1.2
+                  ...
+             dut.192.168.1.1: ssh root@192.168.1.1
+             dut.192.168.1.1: ssh root@192.168.1.1
+             ...
+             dut.192.168.1.1: scp -v dep/dpdk.tar.gz root@192.168.1.1:/tmp/
+             ...
+             dut.192.168.1.1: DUT PORT MAP: [0, 1]
+             ...
+             dut.192.168.1.1: export RTE_TARGET=x86_64-native-linuxapp-gcc
+             dut.192.168.1.1: export RTE_SDK=`pwd`
+             dut.192.168.1.1: rm -rf x86_64-native-linuxapp-gcc
+             dut.192.168.1.1: CC=gcc meson -Denable_kmods=True -Dlibdir=lib  --default-library=static x86_64-native-linuxapp-gcc
+             ...
+             dut.192.168.1.1: usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:af:00.0 0000:af:00.1
+                        dts: NIC :        fortville_25g
+             dut.192.168.1.1: meson configure -Dexamples=helloworld x86_64-native-linuxapp-gcc
+             dut.192.168.1.1: ninja -C x86_64-native-linuxapp-gcc
+             dut.192.168.1.1: ls x86_64-native-linuxapp-gcc/examples/dpdk-helloworld
+                TestHelloWorld: Test Case test_hello_world_all_cores Begin
+             dut.192.168.1.1: cat config/defconfig_x86_64-native-linuxapp-gcc | sed '/^#/d' | sed '/^\s*$/d'
+             dut.192.168.1.1: ./x86_64-native-linuxapp-gcc/examples/dpdk-helloworld  -l 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71 -n 4   --file-prefix=dpdk_25703_20210311003827
+                TestHelloWorld: Test Case test_hello_world_all_cores Result PASSED:
+                TestHelloWorld: Test Case test_hello_world_single_core Begin
+             dut.192.168.1.1: ./x86_64-native-linuxapp-gcc/examples/dpdk-helloworld  -l 1 -n 4   --file-prefix=dpdk_25703_20210311003827
+                TestHelloWorld: Test Case test_hello_world_single_core Result PASSED:
+                           dts:
+    TEST SUITE ENDED: TestHelloWorld
+             ...
+             dts: DTS ended
+    [root@tester ~]#
+
+Check Test Result
+==================
+
+The result files are generated in dts/output.
+
+.. code-block:: console
+
+   [root@tester output]# ls
+   rst_report  dts.log  statistics.txt  TestHelloWorld.log  test_results.json  test_results.xls
+
+*   statstics.txt: summary statistics
+
+.. code-block:: console
+
+   [root@tester output]# cat statistics.txt
+   dpdk_version = 21.02.0
+   Passed     = 2
+   Failed     = 0
+   Blocked    = 0
+   Pass rate  = 100.0
+
+*   test_result.json: json format result file
+
+.. code-block:: console
+
+   [root@tester output]# cat result.json
+    {
+        "192.168.1.1": {
+            "dpdk_version": "21.02.0",
+            "nic": {
+                "driver": "vfio-pci",
+                "firmware": "8.00 0x80008c1a 1.2766.0",
+                "kdriver": "i40e-2.13.10",
+                "name": "fortville_25g"
+            },
+            "x86_64-native-linuxapp-gcc": {
+                "hello_world/test_hello_world_all_core": "passed"
+                "hello_world/test_hello_world_single_core": "passed"
+            }
+        }
+    }
+
+*   test_result.xls: excel format result file
+
+.. figure:: image/dts_result.png
diff --git a/doc/dts_gsg/review.rst b/doc/dts_gsg/review.rst
deleted file mode 100644
index b48cd1d..0000000
--- a/doc/dts_gsg/review.rst
+++ /dev/null
@@ -1,104 +0,0 @@
-Review Test Result
-==================
-
-Browse the result files
------------------------
-After DPDK Test Suite finished the validation, we can find the result files as below in output folder. The files in output folder maybe different when change the CRB or choose different suites.
-
-For Example, You can find the following in output folder after execution.
-
-.. code-block:: console
-
-   [root@tester output]# ls
-   CrownPassCRB1  dts.log  statistics.txt  TestHelloWorld.log  test_results.xls
-
-Please see details about these files:
-
-*   CrownPassCRB1: contains the result RST file and graph of performance data
-*   dts.log: Full execution log of DPDK Test Suite framework  
-*   statstics.txt: summary statistics of DPDK Test Suite executed suites 
-*   TestHelloWorld.log: log message of TestHelloWorld case
-*   test_result.xls: excel format result file
-
-Check test result of DPDK Test Suite
-------------------------------------
-
-You can go through the summary of execution result via statistic.txt. This file includes the number of passed test cases, the number of failed case, the number of blocked and pass ratio. 
-
-Please see example as the following. You can cat the sample file, then show this information of execution, totally executed two test cases, all cases passed the criterion and no failed or blocked cases.
-
-.. code-block:: console
-
-   [root@tester output]# cat statistics.txt
-   Passed     = 2
-   Failed     = 0
-   Blocked    = 0
-   Pass rate  = 100.0
-
-If you need more detail information of test result, please open excel formatted file test_result.xls. This file contains of both detailed case information and case results. Also you can find description of the failure reason if DPDK Test Suite can track it.
-
-.. figure:: image/dts_result.png
-
-If you want to track more details about the process of each suite, please go to log file which named by this suite, all related information will stored in this file.
-
-DPDK Test Suite log module provides several levels to track event or output in log file. Every message level will have its own scopes.  Separated log messages will help us get to known what happening in DPDK Test Suite and what happening in DUT and tester.
-
-
-.. table::
-
-    +---------------------+---------------------------------------------------------------------------------------------+
-    | Level               | description                                                                                 |
-    +---------------------+---------------------------------------------------------------------------------------------+
-    | INFO                | DPDK Test Suite system level log, show start and stop process in this suite                 |
-    +---------------------+---------------------------------------------------------------------------------------------+
-    | SUITE_DUT_CMD       | Commands send to DUT CRB                                                                    |
-    +---------------------+---------------------------------------------------------------------------------------------+
-    | SUITE_DUT_OUTPUT    | Output after the send the commands to DUT                                                   |
-    +---------------------+---------------------------------------------------------------------------------------------+
-    | SUITE_TESTER_CMD    | Commands send to tester, most of they are Scapy commands which will send packet to DUT port |
-    +---------------------+---------------------------------------------------------------------------------------------+
-    | SUITE_TESTER_OUTPUT | Output after the send the commands to tester                                                |
-    +---------------------+---------------------------------------------------------------------------------------------+
-    
-
-Please see example for TestHelloWorld suite log as the following. This log file showed that application helloworld sent hello message from core1, and finally matched the pass criterion.
-
-.. code-block:: console
-
-   22/08/2014 11:04:45                 INFO:
-   TEST SUITE : TestHelloWorld
-   22/08/2014 11:04:45                 INFO: NIC :        niantic
-   22/08/2014 11:04:45        SUITE_DUT_CMD: make -j -C examples/helloworld
-   22/08/2014 11:04:45     SUITE_DUT_OUTPUT: make: Entering directory `/root/dpdk/examples/helloworld'^M
-     CC main.o^M
-     LD helloworld^M
-     INSTALL-MAP helloworld.map^M
-     INSTALL-APP helloworld^M
-   make: Leaving directory `/root/dpdk/examples/helloworld'
-   22/08/2014 11:04:45                 INFO: Test Case test_hello_world_single_core Begin
-   22/08/2014 11:04:45        SUITE_DUT_CMD: ./examples/helloworld/build/app/helloworld -n 1 -c 0x1fffffffff
-   22/08/2014 11:04:48     SUITE_DUT_OUTPUT: EAL: Detected lcore 0 as core 0 on socket 0^M
-   …
-   hello from core 1
-   22/08/2014 11:05:08                 INFO: Test Case test_hello_world_single_core Result PASSED:
-   22/08/2014 11:05:09        SUITE_DUT_CMD: uname
-   22/08/2014 11:05:09     SUITE_DUT_OUTPUT:
-   22/08/2014 11:05:09     SUITE_TESTER_CMD: killall scapy 2>/dev/null; echo tester
-   22/08/2014 11:05:09  SUITE_TESTER_OUTPUT: tester
-   22/08/2014 11:05:10     SUITE_TESTER_CMD: uname
-   22/08/2014 11:05:10  SUITE_TESTER_OUTPUT:
-   22/08/2014 11:05:10                 INFO:
-   TEST SUITE ENDED: TestHelloWorld
-
-Generate PDF doc from RST
--------------------------
-
-Since DPDK Test Suite stores test result as RST by default, you may be want to transfer it to PDF formatted which make it more readable. Firstly, please enter the folder which contained the RST results, then use python tool ``rst2pdf`` to convert RST. If there’s no error return, you can find the pdf file generated with same name.
-
-.. code-block:: console
-
-   [root@tester dts]# cd output/CrownPassCRB1/x86_64-native-linuxapp-gcc/Niantic
-   [root@tester niantic]# rst2pdf TestResult_hello_world.rst
-   [root@tester niantic]# ls
-    TestResult_hello_world.pdf  TestResult_hello_world.rst
-
diff --git a/doc/dts_gsg/scenario.rst b/doc/dts_gsg/scenario.rst
deleted file mode 100644
index c13fb89..0000000
--- a/doc/dts_gsg/scenario.rst
+++ /dev/null
@@ -1,152 +0,0 @@
-Virtualization Scenario
-=======================
-
-When enable virtualization scenario setting in execution cfg, DTS will load scenario configurations and prepare resource and devices for VMs. After VMs started, scenario module will prepare test suite running environment. After all suites finished, scenario module will stop VMs and then clean up the scene.
-
-Configuration File
-------------------
-
-With below configuration, DTS will create one scenario which created one VM with two VF devices attached. In scene section and according to configurations defined in suite. DUT object in suite will be VM DUT object, tester and DUT port network topology will be discovered automatically. Now DTS only support kvm typed hypervisor to create virtualization scenario.
-
-
-.. code-block:: console
-
-	# vm configuration for vf passthrough cases
-	# numa 0,1,yes yes mean cpu numa match the first port
-	# skipcores list mean those core will not be used by vm
-	# dut=vm_dut; mean vm_dut act as dut
-	# dut=dut; mean host dut act as dut
-	# portmap=cfg; mean vm_dut port map will be load from cfg
-	# portmap=auto; mean vm_dut will create portmap automatically
-	# devices = dev_gen/host/dev_gen+host not useful now
-	[scene]
-	suite =
-		dut=vm_dut,portmap=auto;
-		tester=tester;
-	type=kvm;
-
-Virtual machine "vm0" section configured cpu, memory, disk and device settings in VM. As below configurations, VM will not use the first four lcores on DUT. DTS will generate two VF devices from first two host PF devices. These two VF devices will be pass-through into guest and their pci address will be auto assigned by qemu.
-
-.. code-block:: console
-
-	[vm0]
-	cpu =
-		model=host,number=4,numa=auto,skipcores=0 1 2 3;
-	mem =
-		size=2048,hugepage=no;
-	disk =
-		file=/storage/vm-image/vm0.img;
-	dev_gen =
-		pf_idx=0,vf_num=1,driver=default;
-		pf_idx=1,vf_num=1,driver=default;
-	device =
-		vf_idx=0,pf_dev=0,guestpci=auto;
-		vf_idx=0,pf_dev=1,guestpci=auto;
-	vnc =
-	displayNum=1;
-
-All suites will be run in scenario like below picture.
-
-.. figure:: image/scene_pf_passthrough.svg
-
-Scenario Parameters
--------------------
-
-Options for suite:
-
-.. table::
-
-	+------------------+----------------------------------+-----------------+---------------+-----------+
-	| option           | Description                      | Options         | Default value | Must have |
-	+------------------+----------------------------------+-----------------+---------------+-----------+
-	| dut              | type of dut for dts suite        | vm_dut,dut      | dut           | No        |
-	+------------------+----------------------------------+-----------------+---------------+-----------+
-	| dut->portmap     | method to generate dut port maps | auto, cfg       | auto          | No        |
-	+------------------+----------------------------------+-----------------+---------------+-----------+
-	| tester           | type of tester for dts suite[Not | N/A             | N/A           | No        |
-	|                  | used by now]                     |                 |               |           |
-	+------------------+----------------------------------+-----------------+---------------+-----------+
-	| type             | type of hypervisor               | kvm,libvirtd    | kvm           | No        |
-	+------------------+----------------------------------+-----------------+---------------+-----------+
-
-Options for cpu:
-
-.. table::
-
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-    | option           | Description                      | Options         | Default value | Must have |
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-    | model            | type of dut for dts suite        |                 | host          | Yes       |
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-    | number           | number of cores in virtual       |                 | 4             | Yes       | 
-    |                  | machine                          |                 |               |           |
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-    | numa_aware       | numa id of cores allocated from  | 0,1,auto        | 0             | Yes       |
-    |                  | resource module                  |                 |               |           |
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-    | skipcores        | cores should not be used, most   |                 |               | No        |
-    |                  | time for those cores will be used|                 |               |           |
-    |                  | by dpdk on host                  |                 |               |           |
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-
-Options for mem:
-
-.. table::
-
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-    | option           | Description                      | Options         | Default value | Must have |
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-    | size             | virtual machine memory size in   |                 | 2048          | Yes       | 
-    |                  | MBs                              |                 |               |           |
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-    | hugepage         | whether allocate memory from     |                 | No            | No        |
-    |                  | hugepages                        |                 |               |           |
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-
-Options for dev_gen:
-
-.. table::
-
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-    | option           | Description                      | Options         | Default value | Must have |
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-    | pf_idx           | PF device index of host port     |                 | 0             | Yes       | 
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-    | pf_inx->vf_num   | number of VFs created by this PF |                 | 0             | Yes       |
-    |                  | device                           |                 |               |           |
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-    | pf_inx->driver   | Allocate VF devices from which PF| igb_uio,default | default       | Yes       |
-    |                  | host driver                      | vfio-pci        |               |           |
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-
-Options for device:
-
-.. table::
-
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-    | option           | Description                      | Options         | Default value | Must have |
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-    | pf_idx           | PF device index of host port     |                 | 0             | Yes       |
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-    | pf_idx->guestpci | pci address in virtual machine   |                 |               | No        |
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-    | vf_idx           | VF devices index of all VFs      |                 |               | No        |
-    |                  | belong to same PF devices        |                 |               |           |
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-    | vf_idx->pf_dev   | PF device index of this VF device|                 |               | Yes       |
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-    | vf_idx->guestpci | pci address in virtual machine   |                 |               | No        |
-    +------------------+----------------------------------+-----------------+---------------+-----------+
-
-Options for ports:
-
-.. table::
-
-	+------------------+----------------------------------+-----------------+---------------+-----------+
-	| option           | Description                      | Options         | Default value | Must have |
-	+------------------+----------------------------------+-----------------+---------------+-----------+
-	| dev_idx          | device index of virtual machine  |                 |               | No        |
-	|                  | ports                            |                 |               |           |
-	+------------------+----------------------------------+-----------------+---------------+-----------+
-	| dev_idx->peer    | tester peer port's pci address   |                 |               | No        |
-	+------------------+----------------------------------+-----------------+---------------+-----------+
diff --git a/doc/dts_gsg/support_igb_uio.rst b/doc/dts_gsg/support_igb_uio.rst
deleted file mode 100644
index ca48a8f..0000000
--- a/doc/dts_gsg/support_igb_uio.rst
+++ /dev/null
@@ -1,102 +0,0 @@
-Test DPDK based on igb_uio
-==========================
-
-The kernel module igb_uio is moved to the dpdk-kmods repository in the
-/linux/igb_uio/ directory snice DPDK 20.11 (commit: 56bb5841fd06).
-The most easy way to test DPDK in DTS based on igb_uio is to add igb_uio
-source code back to dpdk.
-
-
-Get Source Code
----------------
-
-Get DPDK::
-
-   git clone git://dpdk.org/dpdk
-   git clone http://dpdk.org/git/dpdk
-
-Get igb_uio::
-
-   git clone http://dpdk.org/git/dpdk-kmods
-   git clone git://dpdk.org/dpdk-kmods
-
-Integrate igb_uio into DPDK
----------------------------
-
-Assume you have cloned the dpdk and dpdk-kmods source code
-in ./dpdk and ./dpdk-kmods.
-
-#. Copy dpdk-kmods/linux/igb_uio/ to dpdk/kernel/linux/::
-
-    [root@dts linux]# cp -r ./dpdk-kmods/linux/igb_uio /root/dpdk/kernel/linux/
-    [root@dts linux]# ls ./dpdk/kernel/linux/
-    igb_uio  kni  meson.build
-
-#. enable igb_uio build in meson:
-
-*   add igb_uio in dpdk/kernel/linux/meson.build subdirs as below::
-
-     subdirs = ['kni', 'igb_uio']
-
-.. note::
-
-    igb_uio will be added into compile list when it is added in subdirs.
-
-
-*   create a file of meson.build in dpdk/kernel/linux/igb_uio/ as below::
-
-     # SPDX-License-Identifier: BSD-3-Clause
-     # Copyright(c) 2017 Intel Corporation
-
-     mkfile = custom_target('igb_uio_makefile',
-             output: 'Makefile',
-             command: ['touch', '@OUTPUT@'])
-
-     custom_target('igb_uio',
-             input: ['igb_uio.c', 'Kbuild'],
-             output: 'igb_uio.ko',
-             command: ['make', '-C', kernel_dir + '/build',
-                     'M=' + meson.current_build_dir(),
-                     'src=' + meson.current_source_dir(),
-                     'EXTRA_CFLAGS=-I' + meson.current_source_dir() +
-                             '/../../../lib/librte_eal/include',
-                     'modules'],
-             depends: mkfile,
-             install: true,
-             install_dir: kernel_dir + '/extra/dpdk',
-             build_by_default: get_option('enable_kmods'))
-
-.. note::
-
-    DPDK is using meson build, create meson.build so that igb_uio can be built.
-
-DTS configuration
------------------
-
-#. Pack the dpdk into dpdk.tar.gz and copy into dts/dep::
-
-    tar -zcvf dpdk.tar.gz dpdk
-    cp dpdk.tar.gz ~/dts/dep
-
-
-#. config drivername=igb_uio in execution.cfg::
-
-    [Execution1]
-    crbs=127.0.0.1
-    drivername=igb_uio
-    build_type=meson
-    test_suites=
-        checksum_offload,
-    targets=
-        x86_64-native-linuxapp-gcc
-    parameters=nic_type=cfg:func=true
-
-#. configure dts with other requirements (not mentioned here) and now start dts::
-
-   ./dts
-
-.. note ..
-
-    dts parameter "-s" means skip setup, it won't unpack dep/dpdk.tar.gz
-    to the default directory `/root/dpdk`, but use dpdk already there.
-    so copy the integrated dpdk to `/root/dpdk` if with `-s`
\ No newline at end of file
diff --git a/doc/dts_gsg/sys_reqs.rst b/doc/dts_gsg/sys_reqs.rst
deleted file mode 100644
index c549646..0000000
--- a/doc/dts_gsg/sys_reqs.rst
+++ /dev/null
@@ -1,202 +0,0 @@
-System Requirements
-===================
-
-The board assigned to be tester should be installed the latest Fedora distribution for easily installed DPDK Test Suite required python modules. Tester board needs plug at least 2 x Intel® 82599 (Niantic) NICs (2x 10GbE full duplex optical ports per NIC) in the PCI express slots, then connect these four Niantic ports to the DUT board and make sure the link has been started up and speed is 10000Mb/s.
-
-Beside the four Niantic ports, tester and DUT should also have one interface connected to the same intranet. So that they can be accessed by each other from local IP address.
-
-.. note::
-
-   Firewall should be disabled that all packets can be accepted by Niantic Interface.
-
-.. code-block:: console
-
-   systemctl disable firewalld.service
-
-Setup Tester Environment
-------------------------
-
-.. note::
-
-   Please install the latest ubuntu distribution on the tester before install DPDK Test Suite on tester. Currently we recommend ubuntu 18.04 for tester. The setup instruction and required packages may be different on different operation systems.
-
-To enable tester environment, you need to install script language, tool chain and third party packet generator, etc.
-
-Please follow the guidance to finish install as the below section.
-
-SSH Service
-~~~~~~~~~~~
-Since DPDK Test Suite Tester communicates with DUT via SSH, please install and start sshd service in your tester.
-
-.. code-block:: console
-
-   apt-get install sshd                # download / install ssh software
-   systemctl enable ssh                # start ssh service
-
-For create authorized login session, user needs to generate RSA authentication keys to ssh connection.
-
-Please use the following commands:
-
-.. code-block:: console
-
-   ssh-keygen -t rsa
-
-TCL Language Support modules
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Since some third party tools required TCL (Tool Command Language) supports, please install TCL package to control and connect third party package generator. (For example, third-party professional tester IXIA required TCL support)
-
-.. code-block:: console
-
-   apt-get install tcl                 # download / install tcl software
-
-Install Third Party python modules
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-With third party module, DPDK Test Suite is able to export test result as MS Excel file or graphs. To support this feature, please install the following modules in the tester.
-Python Module “xlwt”: this module is used to generate spreadsheet files which compatible with MS Excel 97/2000/XP/2003 XLS files.
-Python Module “numpy”: this module provides method to deal with array-processing test results.
-Python Module “pexpect”: this module provides API to automate interactive SSH sessions.
-Python Module “docutils”: Docutils is a modular system for processing documentation into useful formats, such as HTML, XML, and LaTeX.
-Python Module “pcapy”: Pcapy is a Python extension module that interfaces with the libpcap packet capture library. Pcapy enables python scripts to capture packets on the network.
-Python Module “xlrd”: Xlrd is a Python module that extracts data from Excel spreadsheets.
-Python Module “threadpool”: Threadpool is a Python module that maintains a pool of worker threads to perform time consuming operations in parallel.
-
-Please see installation instruction as the following:
-
-
-.. code-block:: console
-
-   apt-get install python3-pip
-   pip3 install -r ../../requirements.txt
-
-Setup and configure Scapy
-~~~~~~~~~~~~~~~~~~~~~~~~~
-Scapy is a powerful interactive packet manipulation program. It is able to forge or decode packets of a wide number of protocols, send them on the wire, capture them, match requests and replies, and much more. It can easily handle most classical tasks like scanning, tracerouting, probing, unit tests, attacks or network discovery.
-
-DTS uses python module scapy to forge or decode packets of a wide number of protocols, send them over the wire, capture them, and analyse the packets.
-
-.. code-block:: console
-
-   pip3 install scapy
-
-scapy 2.4.4: support packet layer PFCP and GTPPDUSessionContainer
-
-.. code-block:: console
-
-   pip3 install scapy==2.4.4
-
-.. note::
-    There are some differences between scapy 2.4.4 and scapy 2.4.3 about the packet layer, the details refer to the
-    table as follows.
-
-.. table::
-
-    +------------------------+---------------------------------+-----------------------------------------------+------------------------------------------------------+
-    | Compare scapy 2.4.3 with scapy 2.4.4                                                                                                                            |
-    +------------------------+---------------------------------+-----------------------------------------------+------------------------------------------------------+
-    | Layer                  | packet in scapy 2.4.3           | packet in scapy 2.4.4                         | Comments                                             |
-    +========================+=================================+===============================================+======================================================+
-    | PPP                    | PPP(proto=0xc021)               | PPP(b\'\\xc0\\x21\')                          | PPP protocol filed length is 1 byte in scapy2.4.4    |
-    +------------------------+---------------------------------+-----------------------------------------------+------------------------------------------------------+
-    | L2TP                   | L2TP(\'\\x00\\x00\\x00\\x11\')  | L2TP(b\'\\x00\\x00\\x00\\x11\')               | L2TP is byte type in scapy2.4.4                      |
-    +------------------------+---------------------------------+-----------------------------------------------+------------------------------------------------------+
-    | PFCP                   | N/A                             | PFCP(S=1, seid=1)                             | PFCP is not supported in scapy2.4.3                  |
-    +------------------------+---------------------------------+-----------------------------------------------+------------------------------------------------------+
-    | GTPPDUSessionContainer | N/A                             | GTPPDUSessionContainer(type=0, P=1, QFI=0x34) | GTPPDUSessionContainer is not supported in scapy2.4.3|
-    +------------------------+---------------------------------+-----------------------------------------------+------------------------------------------------------+
-
-
-Install DPDK Test Suite on tester
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-After configure environment, we need to install DPDK Test Suite into tester. First of all, download the latest DPDK Test Suite code from remote repo.
-
-.. code-block:: console
-
-   [root@tester ~]#  git clone http://dpdk.org/git/tools/dts
-   [root@tester ~]#  cd dts
-   [root@tester dts]#  ls
-   [root@tester dts]# conf  dep  doc  dts  executions  framework  nics  output  test_plans  tests  tools
-
-High Precision Timer (HPET) must be enabled in the platform BIOS if the HPET is to be used. Otherwise, the Time Stamp Counter (TSC) is used by default. The user can then navigate to the HPET option. On the Crystal Forest platform BIOS, the path is:
-**Advanced -> PCH-IO Configuration -> High Precision Timer**
-
-The DPDK Test Suite is composed of several file and directories:
-
-*   dts: Main module of DPDK Test Suite suite
-*   exectution.cfg: configuration file of DPDK Test Suite suite
-*   framework: folder with dts framework modules
-*   nics: folder with different network device modules
-*   output: folder which contain running log files and result files
-*   test_plans: folder with rst files which contain the description of test case
-*   tests: folder with test case scripts
-
-Setup Target Environment
-------------------------
-
-This section describes how to deploy DPDK Test Suite packages into DUT target.So far, DPDK Test Suite supports the following OS on DUT:
-
-*   Fedora 32
-*   Ubuntu 16.04/18.04/20.04
-*   FreeBSD 12.1
-*   RedHat 7.7/8.0
-*   SUSE 15
-*   Centos 7.7/8.0
-*   OpenWRT 19.07
-
-Before run DPDK Test Suite on target, we need to configure target environment, it includes BIOS setting, Network configure, compiler environment, etc.
-
-BIOS setting Prerequisite
-~~~~~~~~~~~~~~~~~~~~~~~~~
-
-In general, enter BIOS Menu by pressing F2 while the platform is starting up.
-
-.. note::
-   It is strongly recommended to use DPDK with the latest generation of Intel platforms and processors.
-
-The High Precision Timer (HPET) must be enabled in the platform BIOS if the HPET is to be used. Otherwise, the Time Stamp Counter (TSC) is used by default. The user can then navigate to the HPET option. On the Crystal Forest platform BIOS, the path is:
-
-**Advanced -> PCH-IO Configuration -> High Precision Timer**
-
-Enhanced Intel SpeedStep® Technology must be disabled in the platform BIOS, to ensure the processor voltage and core frequency do not change. This is necessary for consistency of data. On the Crystal Forest platform BIOS the path is:
-
-
-**Advanced -> Processor Configuration -> Enhanced Intel SpeedStep**
-
-Processor state C3 and C6 must be disabled for performance measure too. On the Crystal Forest platform BIOS, the path is:
-
-**Advanced -> Processor Configuration -> Processor C3**
-**Advanced -> Processor Configuration -> Processor C6**
-
-Hyper-Threading Technology must be enabled. On the Crystal Forest platform BIOS, the path is:
-
-**Advanced -> Processor Configuration -> Intel® Hyper-Threading Tech**
-
-If the platform BIOS has any particular performance option, select the settings for best performance.
-
-DPDK running Prerequisite
-~~~~~~~~~~~~~~~~~~~~~~~~~
-Compilation of DPDK need GNU maker, gcc, libc-header, kernel header installed. For 32-bit compilation on 64-bit systems, there’re some additional packages required. For Intel® C++ Compiler (icc) additional libraries may be required. For more detail information of required packets, please refer to Data Plane Development Kit Getting Started Guide.
-
-The  DPDK igb_uio kernel module depends on traditional Linux kernel ``uio`` support to operate. Linux traditional ``uio`` support may be compiled as a module, so this module should be loaded using the ``modprobe`` program.
-Kernel must support the allocation of hugepages. Hugepage support is required for the large memory pool allocation used for packet buffers. By using hugepage allocations, performance will be improved  since only fewer pages are needed, and therefore less Translation Lookaside Buffers (TLBs, high speed translation caches), which reduce the time it takes to translate a virtual page address to a physical page address. Without hugepages, high TLB miss rates would occur, slowing performance.
-
-For more detail information of system requirements, also refer to `Data Plane Development Kit Getting Started Guide <http://dpdk.org/doc/guides>`_.
-
-Authorized login session
-------------------------
-In DPDK Test Suite, support communication be established based on authorized ssh session. All ssh connection to each other will skip password interactive phase if remote server has been authorized.
-
-In tester, you can use tool ssh-copy-id to save local available keys on DUT, thus create authorise login session between tester and DUT. By the same way, you can create authorise login session between tester and itself.
-
-.. code-block:: console
-
-   ssh-copy-id -i “IP of DUT”
-   ssh-copy-id -i “IP of tester”
-
-In DUT, You also can use tool ssh-copy-id to save local available keys in tester, thus create authorise login session between DUT and tester.
-
-.. code-block:: console
-
-   ssh-copy-id –i “IP of Tester”
-
diff --git a/doc/dts_gsg/trex.rst b/doc/dts_gsg/trex.rst
deleted file mode 100644
index 4676f96..0000000
--- a/doc/dts_gsg/trex.rst
+++ /dev/null
@@ -1,23 +0,0 @@
-Configuring T-Rex for DPDK Test Suite
-=====================================
-
-DPDK can utilize T-Rex as a traffic generator in stateless Layer 2 mode.
-
-An example T-Rex configuration that accomplishes this is shown as follows:
-
-.. code-block:: console
-
-  - port_limit: 2
-    version: 2
-    interfaces: ["03:00.0", "03:00.1"]
-    port_info:
-            - src_mac: "aa:bb:cc:dd:ee:ff"
-              dest_mac: "ff:ee:dd:cc:bb:aa"
-            - src_mac: "ff:ee:dd:cc:bb:aa"
-              dest_mac: "aa:bb:cc:dd:ee:ff"
-
-DTS may use a standalone T-Rex instance, or can be configured to start T-Rex
-itself using the settings in ``pktgen.conf``.
-
-To read more about T-Rex stateless mode, read the
-`T-Rex stateless support guide <https://trex-tgn.cisco.com/trex/doc/trex_stateless.html>`__.
diff --git a/doc/dts_gsg/trex_known_issue.rst b/doc/dts_gsg/trex_known_issue.rst
deleted file mode 100644
index 8a84e7c..0000000
--- a/doc/dts_gsg/trex_known_issue.rst
+++ /dev/null
@@ -1,113 +0,0 @@
-======================
-How dts work with trex
-======================
-
-dpdk hugepage management conflict issue
-=======================================
-trex use older dpdk version than we release cycle source code. When dpdk change
-the memory management merchanism, trex will meet the following issue.
-
-Trex should run on an independent platform. DUT/Trex should run on two platforms:
-
-* one is used as TESTER and trex server, another one is used as DUT.(dts/pktgen)
-* one is used as trex server, another one is used as DUT/TESTER.(recommended scheme)
-   This scheme can make sure that trex run on its full status capability.
-
-When trex run with dts on the same platform, trex server sometimes boot up
-failed for hugepage error.
-
-.. code-block:: console
-
-      ./t-rex-64  -i --stl -k 4
-
-         Starting Scapy server..... Scapy server is started
-         Trying to bind to igb_uio ...
-         /usr/bin/python3 dpdk_nic_bind.py --bind=igb_uio 0000:85:00.0 0000:8a:00.1
-         The ports are bound/configured.
-         Starting  TRex v2.41 please wait  ...
-         EAL: Can only reserve 1766 pages from 4096 requested
-         Current CONFIG_RTE_MAX_MEMSEG=256 is not enough
-         Please either increase it or request less amount of memory.
-         EAL: FATAL: Cannot init memory
-
-         EAL: Cannot init memory
-
-          You might need to run ./trex-cfg  once
-         EAL: Error - exiting with code: 1
-           Cause: Invalid EAL arguments
-
-trex quit when using NNT
-========================
-when bind dut NNT port to igb_uio, peer port will get a link down status, then
-trex server using NNT nic will quit.
-
-.. code-block:: console
-
-   WATCHDOG: task 'master' has not responded for more than 2.00044 seconds - timeout is 2 seconds
-
-   *** traceback follows ***
-
-   1       0x55a7c779561a ./_t-rex-64(+0x12761a) [0x55a7c779561a]
-   2       0x7f23da4be1b0 /lib64/libpthread.so.0(+0x121b0) [0x7f23da4be1b0]
-   3       0x55a7c7942d40 rte_delay_us_block + 128
-   4       0x55a7c798d731 ixgbe_setup_mac_link_multispeed_fiber + 337
-   5       0x55a7c79a8f14 ./_t-rex-64(+0x33af14) [0x55a7c79a8f14]
-   6       0x55a7c7954c72 rte_eth_link_get_nowait + 114
-   7       0x55a7c776a988 DpdkTRexPortAttr::update_link_status_nowait() + 24
-   8       0x55a7c77856a6 CGlobalTRex::handle_slow_path() + 118
-   9       0x55a7c7785ad7 CGlobalTRex::run_in_master() + 759
-   10      0x55a7c7785e3c ./_t-rex-64(+0x117e3c) [0x55a7c7785e3c]
-   11      0x55a7c793efba rte_eal_mp_remote_launch + 346
-   12      0x55a7c7789e1e main_test(int, char**) + 1038
-   13      0x7f23d9417f2a __libc_start_main + 234
-   14      0x55a7c7719b9d ./_t-rex-64(+0xabb9d) [0x55a7c7719b9d]
-
-
-   *** addr2line information follows ***
-
-   ??:0
-   ??:0
-   ??:0
-   ??:0
-   ??:0
-   ??:0
-   ??:0
-   ??:0
-   ??:0
-   ??:0
-   ??:0
-   ??:0
-   ??:0
-   ??:0
-
-
-   ./t-rex-64: line 80: 25870 Aborted                 (core dumped) ./_$(
-
-scapy name space conflict
-=========================
-trex scapy lib will be conflict with
-
-resolved scheme
----------------
-
-#. backup your scapy::
-   cp -fr /usr/lib/python3/site-packages/scapy /usr/lib/python3/site-packages/scapy_backup
-
-#. unify scapy version with trex::
-   cp -fr /opt/trex/v2.41/trex_client/external_libs/scapy-2.3.1/python3/scapy /usr/lib/python3/site-packages/scapy
-
-other issues
-============
-
-#. linux kernel verion should not be too low.
-
-#. Trex only works with even number link peers.
-
-#. Trex only works with nics, which are using the same driver.
-
-#. Before boot up trex, please make sure the peer ports are on up status.
-
-#. If you have ran dpdk on the platform which you want to deploy trex-server,
-   reboot the platform to make sure that trex-server can work fine.
-
-#. If using i40e driver, Trex v2.41 version need i40e nic firmware version newer than 5.02.
diff --git a/doc/dts_gsg/tutorial.rst b/doc/dts_gsg/tutorial.rst
deleted file mode 100644
index 543c134..0000000
--- a/doc/dts_gsg/tutorial.rst
+++ /dev/null
@@ -1,139 +0,0 @@
-Tutorial
-========
-
-Functional Test Tutorial
-------------------------
-Tutorial of functional test.
-
-Execution configuration
-~~~~~~~~~~~~~~~~~~~~~~~
-By default, DTS will load execution tasks from execution.cfg. In this file, user can assign multiple tasks to DTS. For each task, DTS will initialize dpdk environment on DUT and run test suites listed. As example below, user assigned one execution task on 127.0.0.1.
-
-Details of the task is defined by some settings like target, NIC type, functional or performance case and foremost the list of suites which will be executed.
-
-.. code-block:: console
-
-   [127.0.0.1]
-   crbs=127.0.0.1
-   drivername=igb_uio
-   test_suites=
-       vlan
-   targets=
-   x86_64-native-linuxapp-gcc
-   parameters=nic_type=cfg:func=true
-
-DUT&Tester configuration
-~~~~~~~~~~~~~~~~~~~~~~~~
-In previous chapter, we assume that user has assigned some execution task on 127.0.0.1. DTS will create the SSH connections to the DUT and tester which connected to it in the runtime. After session established, DTS will setup kernel modules and hugepages on DUT. The procedures for different OS maybe different, so type of OS is also needed to be configured by manual.
-
-.. code-block:: console
-
-   cat ./conf/crbs.cfg
-   [127.0.0.1]
-   dut_ip=127.0.0.1
-   dut_user=root
-   dut_passwd=xxx
-   os=linux
-   tester_ip=192.168.1.1
-   tester_passwd=xxx
-   ixia_group=None
-   channels=4
-   bypass_core0=True
-
-Network topology configuration
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-By default DTS will detect network topology automatically, but in certain occasions it can’t be done like no kernel module available for latest NIC or tester’s port need special settings. For resolving those kind of problems, DTS also support manually specify ports connections. The concept is that user only need to specify PCI devices under test and peer PCI address on tester server. In below sample, we defined network topology that DUT pci device (18:00.0) connected to pci device (1b:00.0) on 192.168.1.1. 
-
-.. code-block:: console
-
-   cat ./conf/ports.cfg
-   [127.0.0.1]
-   ports =
-       pci=0000:18:00.0,peer=0000:1b:00.0;
-
-Running execution
-~~~~~~~~~~~~~~~~~
-Before running real task, DPDK release packet should be saved under dep folder. 
-Make sure that files will be extracted to folder name same as default output directory (dpdk).
-
-.. code-block:: console
-
-   cp dpdk.tar.gz dep/
-   ./dts
-
-
-Performance Test Tutorial
--------------------------
-Turtorial of performance test.
-
-Execution configuration
-~~~~~~~~~~~~~~~~~~~~~~~
-Like functional test, performance execution need configure CRB, target, NIC type and suites. Only difference is that performance option should be true in parameters setting.
-
-.. code-block:: console
-
-   [127.0.0.1]
-   crbs=127.0.0.1
-   drivername=igb_uio
-   test_suites=
-       l2fwd
-   targets=
-       x86_64-native-linuxapp-gcc
-   parameters=nic_type=cfg:perf=true
-
-DUT&Tester configuration
-~~~~~~~~~~~~~~~~~~~~~~~~
-DTS now support two kinds of packet generators. One is hardware packet generator IXIA, the other is dpdk based packet generator. Here is the sample for IXIA, IXIA's hardware resource like ports will be managed by groups in DTS. User need to assign which group will be used, and therefore IXIA ports in the group will be extended to tester's ports list.
-
-.. code-block:: console
-
-   cat ./conf/crbs.cfg
-   [127.0.0.1]
-   dut_ip=127.0.0.1
-   dut_user=root
-   dut_passwd=xxx
-   os=linux
-   tester_ip=192.168.1.1
-   tester_passwd=xxx
-   ixia_group=IXIA
-   channels=4
-   bypass_core0=True
-
-.. code-block:: console
-
-   cat ./conf/ixia.cfg
-   [IXIA]
-   ixia_version=6.62
-   ixia_ip=xxx.xxx.xxx.xxx
-   ixia_ports=
-       card=1,port=1;
-       card=1,port=2;
-   ixia_force100g=disable
-
-When there's none IXIA group configured in CRB's cfg file, DTS will try to use dpdk based packet generator for alternative. Apparently dpdk based packet generator can't meet all the requirements like latency,RFC2544 and random packets. The statistics reported by dpdk pktgen were just for reference.
-
-Dpdk based packet generator will request for dpdk running environment. So that user should prepare required kernel module igb_uio.ko under tester's root directory. Due to packet generator can't support one-time build and run on all platforms, user should also prepare pktgen binary under tester's root directory. By now supported combination is dpdk v18.02 + dpdk-pktgen v3.5.0. Download link: http://dpdk.org/browse/apps/pktgen-dpdk/
-
-.. code-block:: console
-
-   cat ./conf/crbs.cfg
-   ...
-   ixia_group=None
-   ...
-
-Network topology configuration
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-By default network topology of IXIA ports can be detected automatically. DTS also support manually configure network topo.
-
-.. code-block:: console
-
-   cat ./conf/ports.cfg
-   [127.0.0.1]
-   ports =
-       pci=0000:18:00.0,peer=IXIA:1.1;
-       pci=0000:18:00.1,peer=IXIA:1.2;
-
-Running execution
-~~~~~~~~~~~~~~~~~
-Same as functional test.
diff --git a/doc/dts_gsg/usage_of_create_eal_and_start_testpmd.rst b/doc/dts_gsg/usage_of_create_eal_and_start_testpmd.rst
deleted file mode 100644
index 144f611..0000000
--- a/doc/dts_gsg/usage_of_create_eal_and_start_testpmd.rst
+++ /dev/null
@@ -1,103 +0,0 @@
-How create_eal_parameters and start_testpmd methods use in DPDK Test Suite
-==========================================================================
-
-create_eal_parameters
-----------------------------
-
-This method used to create EAL parameters character string in DPDK Test Suite.
-for example: -l 1,2 -w 0000:88:00.0 -w 0000:88:00.1 --file-prefix=dpdk_1112_20190809143420.
-
-.. code-block:: console
-
-   define: create_eal_parameters(self, fixed_prefix=False, socket=-1, **config)
-
-   usage and example:
-        no user parameters:
-            param = self.dut.create_eal_parameters()
-            output:
-                param = '-l 1,2 -n 4 -w 0000:1a:00.0 -w 0000:1a:00.1 --file-prefix=dpdk_397938_20191105143309'
-
-        user parameters:
-            1. usage for port and port options, there are two methods for them.
-                param = self.dut.create_eal_parameters(cores='1S/4C/1T', ports=[0,1], port_options={0: "proto_xtr=vlan"})
-                or
-                param = self.dut.create_eal_parameters(cores='1S/4C/1T', ports=['0000:1a:00.0', '0000:1a:00.1'], port_options={'0000:1a:00.0': "proto_xtr=vlan"})
-                output:
-                    param = '-l 1,2,3,4 -n 4 -w 0000:1a:00.0,proto_xtr=vlan -w 0000:1a:00.1  --file-prefix=dpdk_399214_20191105155446'
-
-            2. usage for b_ports.
-                param = self.dut.create_eal_parameters(cores='1S/4C/1T', b_ports=[0])
-                or
-                param = self.dut.create_eal_parameters(cores='1S/4C/1T', b_ports=['0000:1a:00.0'])
-                output:
-                    param = '-l 1,2,3,4 -n 4  -b 0000:1a:00.0 --file-prefix=dpdk_399214_20191105155446'
-
-            3. usage for no-pci.
-                param = self.dut.create_eal_parameters(cores='1S/4C/1T', no_pci=True)
-                output:
-                    param = '-l 1,2,3,4 -n 4 --file-prefix=dpdk_399214_20191105155446 --no-pci'
-
-            4. usage for prefix, if fixed_prefix = True, the file-prefix will use the value of prefix, or the value is dpdk_pid_timestamp.
-                param = self.dut.create_eal_parameters(cores='1S/4C/1T', ports=[0, 1], port_options={0: "proto_xtr=vlan"}, fixed_prefix=True, prefix='user_defined')
-                output:
-                    param = '-l 1,2,3,4 -n 4 -w 0000:1a:00.0,proto_xtr=vlan -w 0000:1a:00.1  --file-prefix=user_defined'
-
-            5. usege for vdevs.
-                param_vdev = self.dut.create_eal_parameters(cores='1S/4C/1T', no_pci=True, vdevs=[r"net_virtio_user0,mac=%s,path=./vhost-net,queues=1"])
-                output:
-                    param = '-l 1,2,3,4 -n 4   --file-prefix=dpdk_399214_20191105155446 --no-pci --vdev net_virtio_user0,mac=%s,path=./vhost-net,queues=1'
-
-
-create_eal_parameters function supports the following parameters:
-
-.. table::
-
-    +---------------------------+---------------------------------------------------+------------------+
-    | parameter                 | description                                       | Default Value    |
-    +---------------------------+---------------------------------------------------+------------------+
-    | fixed_prefix              | Indicate use default prefix or user define prefix | False            |
-    +---------------------------+---------------------------------------------------+------------------+
-    | socket                    | socket of system                                  | -1               |
-    +---------------------------+---------------------------------------------------+------------------+
-    | cores                     | set core list                                     | 1S/2C/1T         |
-    +---------------------------+---------------------------------------------------+------------------+
-    | ports                     | PCI list or PCI ID list                           |                  |
-    +---------------------------+---------------------------------------------------+------------------+
-    | port_options              | other port options                                |                  |
-    +---------------------------+---------------------------------------------------+------------------+
-    | b_ports                   | PCI device in block list                          |                  |
-    +---------------------------+---------------------------------------------------+------------------+
-    | no_pci                    | Disable PCI bug                                   |                  |
-    +---------------------------+---------------------------------------------------+------------------+
-    | prefix                    | Use a different shared data file prefix for a     |                  |
-    |                           | DPDK process                                      |                  |
-    +---------------------------+---------------------------------------------------+------------------+
-    | vdevs                     | Add a virtual device                              |                  |
-    +---------------------------+---------------------------------------------------+------------------+
-
-
-start_testpmd
-----------------------------
-
-The method use to start testpmd application.
-
-.. code-block:: console
-
-   define: start_testpmd(self, cores='default', param='', eal_param='', socket=0, fixed_prefix=False, **config)
-
-   usage and example:
-        no user parameters:
-            out = self.pmdout.start_testpmd()
-        user parameters:
-            1. Those two parameters param and eal_param are used for current test suites.
-                for example:
-                    In current test suite TestSuite_runtime_vf_queue_number, the eal parameters are wrote as a line string as below.
-                        eal_param = '-w %s,queue-num-per-vf=%d --file-prefix=test1 --socket-mem 1024,1024' % (self.pf_pci, invalid_qn)
-                    then you can call start_testpmd like this.
-                        out = self.pmdout.start_testpmd(self.pmdout.default_cores, param='', eal_param=eal_param)
-
-                    Another usage in current test suite like below:
-                        self.pmdout.start_testpmd("Default", "--portmask=%s " %(self.portMask) + " --enable-rx-cksum " + "--port-topology=loop", socket=self.ports_socket)
-
-            2. If you will write a new test suite and need to call start_testpmd method,
-                The usage of other parameters such as cores, socket, fixed_prefix and **config are the same as create_eal_parameters.
diff --git a/doc/dts_gsg/usr_guide/igb_uio.rst b/doc/dts_gsg/usr_guide/igb_uio.rst
new file mode 100644
index 0000000..13648cd
--- /dev/null
+++ b/doc/dts_gsg/usr_guide/igb_uio.rst
@@ -0,0 +1,102 @@
+Practice for igb_uio
+====================
+
+The kernel module igb_uio is moved to the dpdk-kmods repository in the
+/linux/igb_uio/ directory snice DPDK 20.11 (commit: 56bb5841fd06).
+The most easy way to test DPDK in DTS based on igb_uio is to add igb_uio
+source code back to dpdk.
+
+
+Get Source Code
+---------------
+
+Get DPDK::
+
+   git clone git://dpdk.org/dpdk
+   git clone http://dpdk.org/git/dpdk
+
+Get igb_uio::
+
+   git clone http://dpdk.org/git/dpdk-kmods
+   git clone git://dpdk.org/dpdk-kmods
+
+Integrate igb_uio into DPDK
+---------------------------
+
+Assume you have cloned the dpdk and dpdk-kmods source code
+in ./dpdk and ./dpdk-kmods.
+
+#. Copy dpdk-kmods/linux/igb_uio/ to dpdk/kernel/linux/::
+
+    [root@dts linux]# cp -r ./dpdk-kmods/linux/igb_uio /root/dpdk/kernel/linux/
+    [root@dts linux]# ls ./dpdk/kernel/linux/
+    igb_uio  kni  meson.build
+
+#. enable igb_uio build in meson:
+
+*   add igb_uio in dpdk/kernel/linux/meson.build subdirs as below::
+
+     subdirs = ['kni', 'igb_uio']
+
+.. note::
+
+    igb_uio will be added into compile list when it is added in subdirs.
+
+
+*   create a file of meson.build in dpdk/kernel/linux/igb_uio/ as below::
+
+     # SPDX-License-Identifier: BSD-3-Clause
+     # Copyright(c) 2017 Intel Corporation
+
+     mkfile = custom_target('igb_uio_makefile',
+             output: 'Makefile',
+             command: ['touch', '@OUTPUT@'])
+
+     custom_target('igb_uio',
+             input: ['igb_uio.c', 'Kbuild'],
+             output: 'igb_uio.ko',
+             command: ['make', '-C', kernel_dir + '/build',
+                     'M=' + meson.current_build_dir(),
+                     'src=' + meson.current_source_dir(),
+                     'EXTRA_CFLAGS=-I' + meson.current_source_dir() +
+                             '/../../../lib/librte_eal/include',
+                     'modules'],
+             depends: mkfile,
+             install: true,
+             install_dir: kernel_dir + '/extra/dpdk',
+             build_by_default: get_option('enable_kmods'))
+
+.. note::
+
+    DPDK is using meson build, create meson.build so that igb_uio can be built.
+
+DTS configuration
+-----------------
+
+#. Pack the dpdk into dpdk.tar.gz and copy into dts/dep::
+
+    tar -zcvf dpdk.tar.gz dpdk
+    cp dpdk.tar.gz ~/dts/dep
+
+
+#. config drivername=igb_uio in execution.cfg::
+
+    [Execution1]
+    crbs=127.0.0.1
+    drivername=igb_uio
+    build_type=meson
+    test_suites=
+        checksum_offload,
+    targets=
+        x86_64-native-linuxapp-gcc
+    parameters=nic_type=cfg:func=true
+
+#. configure dts with other requirements (not mentioned here) and now start dts::
+
+   ./dts
+
+.. note ..
+
+    dts parameter "-s" means skip setup, it won't unpack dep/dpdk.tar.gz
+    to the default directory `/root/dpdk`, but use dpdk already there.
+    so copy the integrated dpdk to `/root/dpdk` if with `-s`
diff --git a/doc/dts_gsg/usr_guide/image/dts_func_deploy.png b/doc/dts_gsg/usr_guide/image/dts_func_deploy.png
new file mode 100644
index 0000000000000000000000000000000000000000..0062ff79f91891d3704dc97116df69489d757e83
GIT binary patch
diff --git a/doc/dts_gsg/usr_guide/image/dts_result.png b/doc/dts_gsg/usr_guide/image/dts_result.png
new file mode 100644
index 0000000000000000000000000000000000000000..65e0ada586bfb5264eab02f7a6dedfe898e12849
GIT binary patch
diff --git a/doc/dts_gsg/usr_guide/index.rst b/doc/dts_gsg/usr_guide/index.rst
new file mode 100644
index 0000000..f4104f8
--- /dev/null
+++ b/doc/dts_gsg/usr_guide/index.rst
@@ -0,0 +1,42 @@
+..  BSD LICENSE
+        Copyright(c) 2010-2014 Intel Corporation. All rights reserved.
+    All rights reserved.
+
+    Redistribution and use in source and binary forms, with or without
+    modification, are permitted provided that the following conditions
+    are met:
+
+    * Redistributions of source code must retain the above copyright
+    notice, this list of conditions and the following disclaimer.
+    * Redistributions in binary form must reproduce the above copyright
+    notice, this list of conditions and the following disclaimer in
+    the documentation and/or other materials provided with the
+    distribution.
+    * Neither the name of Intel Corporation nor the names of its
+    contributors may be used to endorse or promote products derived
+    from this software without specific prior written permission.
+
+    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+    "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+    LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+    A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+    OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+    SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+    LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+    DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+    THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+    (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+    OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+User Guide
+==========
+
+.. toctree::
+
+    intro
+    sys_reqs
+    usage
+    results
+    trex
+    ixia
+    igb_uio
diff --git a/doc/dts_gsg/usr_guide/intro.rst b/doc/dts_gsg/usr_guide/intro.rst
new file mode 100644
index 0000000..dc4c0bf
--- /dev/null
+++ b/doc/dts_gsg/usr_guide/intro.rst
@@ -0,0 +1,90 @@
+Introduction
+============
+
+This document describes how to install and configure the Data Plane Development Kit Test Suite (DTS) in a Linux environment.
+DTS is an automation test tool for DPDK, wrote in `Python3`.
+DTS includes one set of test cases and DPDK generic test framework.
+DTS provides test example, references and framework for open source community.
+Based on DTS, everyone can develop their test plan, automation script and configuration for own features and platform.
+In addition, DTS provides a solution to allow that DPDK developers contribute their function test to certify their patch integration.
+It only requires limited effort to maintain test cases once merged into DPDK Test Suite.
+Everyone can utilize DTS to measure performance and functionality for features.
+
+As a generic test framework, DTS provides the following functions:
+
+* Communicate/manage DUT and Tester by SSH connection.
+* Able to work with DUT (Device Under Test), which installed Fedora, Ubuntu, CentOS, RHEL, etc.
+* Support virtualization hypervisor Qemu.
+* Support both software and hardware traffic generators, including Scapy, TRex and IXIA®.
+* Provide configure files to customize test suite and test cases to run under DUT.
+* Provide debug and log functionalities for tracking test cases execution process.
+* Support to output test result by excel, json, log text file, etc.
+
+DTS environment includes DUT (Device under Test), Tester and Traffic generator. DPDK are deployed on DUT and DTS can run on the Tester or DUT or the third machine.
+
+.. note::
+
+   * If run with functional testing, DTS uses `Scapy` as traffic generator, recommend installing DTS on Tester.
+   * If run with performance testing, DTS can use `TRex` or IXIA as traffic gengerator based on your deployment and configuration, recommend installing DTS on DUT.
+     * If use `TRex`, recommend deploying `TRex` and DUT on the same machine with different sockets.
+
+Please see a functional deployment example in the following figure:
+
+.. figure:: image/dts_func_deploy.png
+
+This architecture provides automatically mechanism to manage tester, DUT and packet generators, and remove dependency between test script and test environment/hardware.
+It defines one abstraction layer for DPDK Test Suite, and provides extensibility to add more test script.
+In the DPDK Test Suite Test Framework, it provides the following modules to help to manage device, platform, configure and test results.
+
+.. table::
+
+    +---------------------+------------------------------------------------------------------------------+
+    | File Name/Directory | Description                                                                  |
+    +=====================+==============================================================================+
+    | dts                 | Main Application for DTS                                                     |
+    +---------------------+------------------------------------------------------------------------------+
+    | framework           | Folder with dts framework modules                                            |
+    +---------------------+------------------------------------------------------------------------------+
+    | nics                | Folder with different network device modules                                 |
+    +---------------------+------------------------------------------------------------------------------+
+    | conf                | Folder with different config files                                           |
+    +---------------------+------------------------------------------------------------------------------+
+    | execution.cfg       | Default execution file                                                       |
+    +---------------------+------------------------------------------------------------------------------+
+    | executions          | Folder with several execution file samples                                   |
+    +---------------------+------------------------------------------------------------------------------+
+    | output              | Folder which contain running log files and result files                      |
+    +---------------------+------------------------------------------------------------------------------+
+    | dep                 | Folder with dependence scripts                                               |
+    +---------------------+------------------------------------------------------------------------------+
+    | test_plans          | Folder with rst files which contain the description of test suites and cases |
+    +---------------------+------------------------------------------------------------------------------+
+    | tests               | Folder with test scripts for test suites and cases                           |
+    +---------------------+------------------------------------------------------------------------------+
+    | doc                 | Folder with DTS related documents                                            |
+    +---------------------+------------------------------------------------------------------------------+
+    | requirements.txt    | DTS required Python packages                                                 |
+    +---------------------+------------------------------------------------------------------------------+
+
+These test script provides example and reference. Everyone can develop their test cases, verify their features functionality, and commit generic test report to maintainer.
+, user-defined test cases, test plans and scripts must follow DPDK Test Suite standard including code standard, naming conventions, configure format, rst test plan, API.
+
+Please see test cases, which are included in the DPDK compliance test suites:
+
+.. table::
+
+    +---------------------+----------------------------------------------------------------------------------------------------------------------------+
+    | Test Suite          | Descriptions                                                                                                               |
+    +=====================+============================================================================================================================+
+    | hello_world         | Print a ``helloworld`` message on every enabled logic core.                                                                |
+    +---------------------+----------------------------------------------------------------------------------------------------------------------------+
+    | Timer               | Shows how timer can be used in a RTE application.                                                                          |
+    +---------------------+----------------------------------------------------------------------------------------------------------------------------+
+    | checksum_offload    | Tests RX/TX L3/L4 Checksum offload features by Poll Mode Drivers                                                           |
+    +---------------------+----------------------------------------------------------------------------------------------------------------------------+
+    | jumbo_frame         | Tests jumbo frames features by Poll Mode Drivers                                                                           |
+    +---------------------+----------------------------------------------------------------------------------------------------------------------------+
+    | testpmd             | Provides benchmark tests for the Intel Ethernet Controller (Niantic) Poll Mode Driver.                                     |
+    +---------------------+----------------------------------------------------------------------------------------------------------------------------+
+    | L3fwd               | Verifies Layer-3 Forwarding results using ``l3fwd`` application.                                                           |
+    +---------------------+----------------------------------------------------------------------------------------------------------------------------+
diff --git a/doc/dts_gsg/usr_guide/ixia.rst b/doc/dts_gsg/usr_guide/ixia.rst
new file mode 100644
index 0000000..2ad754e
--- /dev/null
+++ b/doc/dts_gsg/usr_guide/ixia.rst
@@ -0,0 +1,248 @@
+Practice with IxExplorer
+========================
+
+This chapter describes a DTS practice with IXIA IxExplorer, which mainly used for performance testing.
+Here we take the performance case nic_single_core as an example.
+
+Configuring your own execution file
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+First of all, you must configure execution.cfg as below:
+
+.. code-block:: console
+
+   [Execution1]
+   crbs=192.168.1.1
+   drivername=vfio-pci
+   test_suites=
+       nic_single_core_perf,
+   targets=
+       x86_64-native-linuxapp-gcc
+   parameters=nic_type=cfg:perf=true
+   build_type=meson
+   rx_mode=avx512
+
+Configure CRB information
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Then please add the detail information about your CRB in conf/crbs.conf as following:
+
+.. code-block:: console
+
+   [192.168.1.1]
+   dut_ip=192.168.1.1
+   dut_user=root
+   dut_passwd=passwd
+   os=linux
+   dut_arch=
+   tester_ip=192.168.1.1
+   tester_passwd=passwd
+   pktgen_group=IXIA
+   channels=4
+   bypass_core0=True
+   dut_cores=
+
+Configure port information
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+ports topology as below:
+
+.. code-block:: console
+
+   IXIA port 0 <---------> DUT port 0
+   IXIA port 1 <---------> DUT port 1
+
+please add port configuration in conf/ports.cfg as following:
+
+.. code-block:: console
+
+   [192.168.1.1]
+   ports =
+       pci=0000:af:00.0,peer=IXIA:3.1;
+       pci=0000:b1:00.0,peer=IXIA:3.2;
+
+Configure pktgen information
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+please configure Pktgen information in conf/pktgen.cfg
+
+.. code-block:: console
+
+   [IXIA]
+   ixia_version=9.00
+   ixia_ip=192.168.2.1
+   ixia_ports=
+       card=3,port=1;
+       card=3,port=2;
+   ixia_force100g=disable
+
+.. note::
+
+    The version of ixia must be consistent with your version of IxExplorer.
+
+
+Configure your own suites
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Performance tests generally have configuration files.
+it's name corresponds to the suite.
+Below is the conf/nic_single_core_perf.cfg configuration file.
+You can set the test parameters according to your test needs.
+
+
+.. code-block:: console
+
+   [suite]
+   update_expected = True
+   test_parameters = {'1C/1T': {64: [512, 2048]},
+                      '1C/2T': {64: [512, 2048]}}
+   rx_desc_16byte = 'y'
+   test_duration = 60
+   accepted_tolerance = 1
+   expected_throughput = {
+        'fortville_spirit': {
+            '1C/1T': {64: {512: 0.00, 2048: 0.00}},
+            '1C/2T': {64: {512: 0.00, 2048: 0.00}}}}
+
+* accepted_tolerance: defines the accepted tolerance between real pps and expected pps.
+* test_parameters: defines the combination of frame size and descriptor numbers,
+  and the pattern is {'frame size': ['descriptor number #1', 'descriptor number #2']}.
+* rx_desc_16byte: 16byte configuration and default by enabled.
+* test_duration: how many seconds each combination performance will be recorded.
+* expected_throughput: it's a dictionary defining expected throughput numbers based on NIC,
+  and the pattern is {'NIC': {'frame size': {'descriptor number': 'excepted throughput'}}}
+  Every user should fill it out with your actual numbers.
+* update_expected: if update_expected==True, and add argument "--update-expected" in bash command,
+  all objects in this file will changed after the run::
+
+   ./dts --update-expected
+
+At the beginning, please change test_parameters according to your requirements,
+then run ./dts --update-expected to get the absolute results which will replace
+the default numbers 0.00 in this configuration.
+So you will have your own private configuration, and could start your tests as usual.
+
+
+Run DTS performance test with IXIA
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Now you can start DTS performance test with IXIA:
+
+.. code-block:: console
+
+    root@test1:~/dts# ./dts
+                  dts:
+    DUT 192.168.1.1
+                        tester: ssh root@192.168.1.1
+                        ...
+    pktgen: ssh root@192.168.1.1
+                        pktgen: tclsh
+                        pktgen: source ./IxiaWish.tcl
+                        pktgen: set ::env(IXIA_VERSION) 9.00
+                        pktgen: package req IxTclHal
+                        pktgen: ixConnectToTclServer 192.168.2.1
+                        pktgen: ixLogin IxiaTclUser
+                        pktgen: ixConnectToChassis 192.168.2.1
+                        pktgen: set chasId [ixGetChassisID 192.168.2.1]
+                        pktgen: ixClearOwnership [list [list 1 3 1] [list 1 3 2]]
+                        pktgen: ixTakeOwnership [list [list 1 3 1] [list 1 3 2]] force
+                        pktgen: stat getLineSpeed 1 3 1
+                        pktgen: stat getLineSpeed 1 3 2
+                        ...
+
+    TestNicSingleCorePerf: Test Case test_perf_nic_single_core Begin
+    TestNicSingleCorePerf: Executing Test Using cores: ['28', '29'] of config 1C/1T
+    TestNicSingleCorePerf: Test running at parameters: framesize: 64, rxd/txd: 512
+    dut.192.168.1.1: x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 28,29 -n 6 -a 0000:af:00.0 -a 0000:b1:00.0 -- -i --portmask=0x3 --rxq=2 --txq=2 --txd=512 --rxd=512 --nb-cores=1
+    dut.192.168.1.1: start
+                   pktgen: stat getLineSpeed 1 1 1
+                   pktgen: stat getLineSpeed 1 1 2
+                   pktgen: scp -v dumppcap.py root@192.168.1.1:~/
+                   pktgen: scapy -c dumppcap.py 2>/dev/null
+                   pktgen: scp -v dumppcap.py root@192.168.1.1:~/
+                   pktgen: scapy -c dumppcap.py 2>/dev/null
+                   pktgen: scp -v dumppcap.py root@192.168.1.1:~/
+                   pktgen: scapy -c dumppcap.py 2>/dev/null
+                   pktgen: scp -v dumppcap.py root@192.168.1.1:~/
+                   pktgen: scapy -c dumppcap.py 2>/dev/null
+                   pktgen: begin traffic ......
+                   tester: scp -v ixiaConfig.tcl root@192.168.1.1:~/
+                   pktgen: source ixiaConfig.tcl
+                   pktgen: begin get port statistic ...
+                   pktgen: stat getRate statAllStats 1 3 2
+                   pktgen: stat cget -framesReceived
+                   pktgen: stat cget -bitsReceived
+                   pktgen: stat cget -oversize
+                   pktgen: stat getRate statAllStats 1 3 1
+                   pktgen: stat cget -framesReceived
+                   pktgen: stat cget -bitsReceived
+                   pktgen: stat cget -oversize
+                   pktgen: stat getRate statAllStats 1 3 2
+                   pktgen: stat cget -framesReceived
+                   pktgen: stat cget -bitsReceived
+                   pktgen: stat cget -oversize
+                   pktgen: stat getRate statAllStats 1 3 1
+                   pktgen: stat cget -framesReceived
+                   pktgen: stat cget -bitsReceived
+                   pktgen: stat cget -oversize
+                   pktgen: throughput: pps_rx 69504677.000000, bps_rx 35586394625.000000
+                   pktgen: ixStopTransmit portList
+                   pktgen: traffic completed.
+      dut.192.168.1.1: stop
+      dut.192.168.1.1: quit
+      TestNicSingleCorePerf: Trouthput of framesize: 64, rxd/txd: 512 is :69.504677 Mpps
+      ...
+
+         TestNicSingleCorePerf:
+      +----------+------------+---------+-------------+---------+---------------------+-----------------------+
+      | Fwd_core | Frame Size | TXD/RXD | Throughput  |  Rate   | Expected Throughput | Throughput Difference |
+      +==========+============+=========+=============+=========+=====================+=======================+
+      | 1C/1T    | 64         | 512     | 69.505 Mpps | 93.414% | 0.000 Mpps          | 69.505 Mpps           |
+      +----------+------------+---------+-------------+---------+---------------------+-----------------------+
+      | 1C/1T    | 64         | 2048    | 51.078 Mpps | 68.649% | 0.000 Mpps          | 51.078 Mpps           |
+      +----------+------------+---------+-------------+---------+---------------------+-----------------------+
+      | 1C/2T    | 64         | 512     | 74.404 Mpps | 99.999% | 0.000 Mpps          | 74.404 Mpps           |
+      +----------+------------+---------+-------------+---------+---------------------+-----------------------+
+      | 1C/2T    | 64         | 2048    | 67.851 Mpps | 91.192% | 0.000 Mpps          | 67.851 Mpps           |
+      +----------+------------+---------+-------------+---------+---------------------+-----------------------+
+         TestNicSingleCorePerf: Test Case test_perf_nic_single_core Result PASSED:
+
+
+Test result
+~~~~~~~~~~~
+
+After the Test Suite finished the validation, we can find the result files as below in output folder.
+
+.. code-block:: console
+
+   fortville_25g_single_core_perf.json  dts.log  TestNicSingleCorePerf.log test_results.json
+
+The performance case will save the data results in the jison file.
+And the pattern is "nic name + suite name.json".
+Below is the json file of nic_single_core:
+
+.. code-block:: console
+
+      vim fortville_25g_single_core_perf.json
+
+      {"test_perf_nic_single_core": [{
+                "performance": [{"name": "Throughput", "value": 69.505, "unit": "Mpps", "delta": 69.505}],
+                "parameters":  [{"name": "Txd/Rxd", "value": 512, "unit": "descriptor"},
+                               {"name": "frame_size", "value": 64, "unit": "bytes"},
+                               {"name": "Fwd_core", "value": "1C/1T"}], "status": "PASS"},
+                {"performance": [{"name": "Throughput", "value": 51.078, "unit": "Mpps", "delta": 51.078}],
+                 "parameters": [{"name": "Txd/Rxd", "value": 2048, "unit": "descriptor"},
+                                {"name": "frame_size", "value": 64, "unit": "bytes"},
+                                {"name": "Fwd_core", "value": "1C/1T"}], "status": "PASS"},
+               {"performance": [{"name": "Throughput", "value": 74.404, "unit": "Mpps", "delta": 74.404}],
+                "parameters": [{"name": "Txd/Rxd", "value": 512, "unit": "descriptor"},
+                                {"name": "frame_size", "value": 64, "unit": "bytes"},
+                                {"name": "Fwd_core", "value": "1C/2T"}], "status": "PASS"},
+               {"performance": [{"name": "Throughput", "value": 67.851, "unit": "Mpps", "delta": 67.851}],
+                "parameters": [{"name": "Txd/Rxd", "value": 2048, "unit": "descriptor"},
+                               {"name": "frame_size", "value": 64, "unit": "bytes"},
+                               {"name": "Fwd_core", "value": "1C/2T"}], "status": "PASS"}]}
+
+
+You can set your own expectations in con/suite.cfg based on the json data.
+If the actual data differs too much from the expected data, the case fails.
diff --git a/doc/dts_gsg/usr_guide/results.rst b/doc/dts_gsg/usr_guide/results.rst
new file mode 100644
index 0000000..3ec08d8
--- /dev/null
+++ b/doc/dts_gsg/usr_guide/results.rst
@@ -0,0 +1,101 @@
+Test Result
+===========
+
+Overview
+--------
+
+After DTS finished the validation, we can find the result files similar as below in output folder.
+
+.. code-block:: console
+
+   rst_report  dts.log  statistics.txt  TestHelloWorld.log  test_results.json  test_results.xls
+
+*   rst_report: contains the result RST file of performance data
+*   dts.log: Full execution log of DTS framework
+*   statstics.txt: summary statistics of DTS executed suites
+*   TestHelloWorld.log: log message of Test suite: HelloWorld
+*   test_result.json: json format result file
+*   test_result.xls: excel format result file
+
+Statistics
+----------
+
+You can go through the summary of execution result via statistic.txt. This file includes the number of passed test cases, the number of failed case, the number of blocked and pass ratio.
+
+Please see example as the following. You can cat the sample file, then show this information of execution, totally executed two test cases, all cases passed the criterion and no failed or blocked cases.
+
+.. code-block:: console
+
+   [root@tester output]# cat statistics.txt
+   dpdk_version = 21.02.0
+   Passed     = 2
+   Failed     = 0
+   Blocked    = 0
+   Pass rate  = 100.0
+
+Details
+-------
+
+DTS provides 2 formats for test results, one is json, and the other is excel.
+If you need more detail information of test result, either of them is good to check.
+Both of them contain case names and results, also the failure reasons.
+
+* JSON result: result.json
+
+.. code-block:: console
+
+    {
+        "192.168.1.1": {
+            "dpdk_version": "21.02.0",
+            "nic": {
+                "driver": "vfio-pci",
+                "firmware": "8.00 0x80008c1a 1.2766.0",
+                "kdriver": "i40e-2.13.10",
+                "name": "fortville_25g"
+            },
+            "x86_64-native-linuxapp-gcc": {
+                "hello_world/test_hello_world_all_core": "passed"
+                "hello_world/test_hello_world_single_core": "passed"
+            }
+        }
+    }
+
+
+* Excel result: test_result.xls
+
+.. figure:: image/dts_result.png
+
+Logs
+----
+
+If you want to track more details about the process of each suite, please go to log file which named by this suite, all related information will stored in this file.
+
+Please see example for TestHelloWorld suite log as the following. This log file showed that application helloworld sent hello message from core1, and finally matched the pass criterion.
+
+.. code-block:: console
+
+   31/12/2020 11:04:00                 INFO:
+   TEST SUITE : TestHelloWorld
+   31/12/2020 11:04:00                 INFO: NIC :       fortville_25g
+   31/12/2020 11:04:00        SUITE_DUT_CMD: meson configure -Dexamples=helloworld x86_64-native-linuxapp-gcc
+   31/12/2020 11:04:01        SUITE_DUT_CMD: ninja -C x86_64-native-linuxapp-gcc
+   31/12/2020 11:04:07     SUITE_DUT_OUTPUT: ninja: Entering directory `x86_64-native-linuxapp-gcc'^M
+     [0/1] Regenerating build files.^M
+     The Meson build system^M
+     Version: 0.55.3^M
+     Source dir: /root/dpdk^M
+     Build dir: /root/dpdk/x86_64-native-linuxapp-gcc^M
+     Build type: native build^
+     …
+     Build targets in project: 998^M
+     Found ninja-1.10.0.git.kitware.jobserver-1 at /usr/local/bin/ninja^M
+     [1/2] Compiling C object examples/dpdk-helloworld.p/helloworld_main.c.o^M
+     [2/2] Linking target examples/dpdk-helloworld
+   31/12/2020 11:04:09                INFO: Test Case test_hello_world_single_core Begin
+   31/12/2020 11:04:13       SUITE_DUT_CMD: ./x86_64-native-linuxapp-gcc/examples/dpdk-helloworld  -l 1 -n 4   --file-prefix=dpdk_10243_20201231110241
+       SUITE_DUT_OUTPUT: EAL: Detected 72 lcore(s)^M
+   …
+   hello from core 1
+   31/12/2020 11:04:15                 INFO: Test Case test_hello_world_single_core Result PASSED:
+   31/12/2020 11:04:25                 INFO:
+   TEST SUITE ENDED: TestHelloWorld
diff --git a/doc/dts_gsg/usr_guide/sys_reqs.rst b/doc/dts_gsg/usr_guide/sys_reqs.rst
new file mode 100644
index 0000000..8b70abb
--- /dev/null
+++ b/doc/dts_gsg/usr_guide/sys_reqs.rst
@@ -0,0 +1,131 @@
+System Requirements
+===================
+
+This chapter describes the packages required to deploy DTS, including Tester and DUT.
+Tester and DUT should have one interface connected to the same internet, so that they can be accessed by each other from local IP address.
+The tester and DUT are recommended to install the latest Centos, Redhat or Ubuntu for easily installing DTS(DPDK Test Suite) or DPDK required modules.
+
+.. note::
+
+   Uubuntu 20.04 are installed for Tester and DUT, and  The setup instruction and required packages may be different on different operation systems.
+
+Firewall should be disabled on Tester and DUT so that all packets can be accepted by NIC Interface.
+
+.. code-block:: console
+
+   systemctl disable firewalld.service
+
+
+SSH Service
+-----------
+
+Since DPDK Test Suite Tester communicates with DUT via SSH, please install and start sshd service in your Tester and DUT.
+
+.. code-block:: console
+
+   apt-get install sshd
+   systemctl enable ssh
+
+Generally DTS use Linux username and password to login, but it also supports to use authorized login.
+For create authorized login session, user needs to generate RSA authentication keys to ssh connectioni:
+
+.. code-block:: console
+
+   ssh-keygen -t rsa
+
+Python modules
+--------------
+
+To run DTS, `Python3` must be installed, and it uses the following packages:
+
+* xlwt: it is used to generate spreadsheet files which compatible with MS Excel 97/2000/XP/2003 XLS files。
+* numpy: it provides method to deal with array-processing test results.
+* pexpect: it provides API to automate interactive SSH sessions.
+* docutils：it is a modular system for processing documentation into useful formats, such as HTML, XML, and LaTeX
+* pcapy: it is a Python extension module that interfaces with the libpcap packet capture library. Pcapy enables python scripts to capture packets on the network.
+* xlrd: it is a Python module that extracts data from Excel spreadsheets.
+* threadpool: it is a Python module that maintains a pool of worker threads to perform time consuming operations in parallel.
+* scapy: it is a Python program that enables the user to send, sniff and dissect and forge network packets.
+
+They are recorded in `requirements.txt`.
+
+.. code-block:: console
+
+   [root@tester ~]# cat requirements.txt
+    ...
+    xlwt==1.3.0
+    pexpect==4.7.0
+    numpy==1.18.5
+    docutils
+    pcapy
+    xlrd
+    scapy==2.4.4
+    threadpool
+
+Recommend installing them quickly with following commands:
+
+.. code-block:: console
+
+   apt-get install python3-pip
+   pip3 install -r ../requirements.txt
+
+DTS uses python module scapy to forge or decode packets of a wide number of protocols, send them over the wire, capture them, and analyse the packets.
+We recommend installing scapy-2.4.4, as some protocol such as PFCP, GTPPDUSessionContainer are supported from this version.
+
+.. code-block:: console
+
+   pip3 install scapy  # install default version
+   pip3 install scapy==2.4.4 # install specific version
+
+Here are some differences between scapy 2.4.4 and scapy 2.4.3 about the packet layer:
+
+.. table:: Differences between scapy 2.4.3 with scapy 2.4.4
+
+    +------------------------+---------------------------------+-----------------------------------------------+-------------------------------------------------------+
+    | Layer                  | packet in scapy 2.4.3           | packet in scapy 2.4.4                         | Comments                                              |
+    +========================+=================================+===============================================+=======================================================+
+    | PPP                    | PPP(proto=0xc021)               | PPP(b\'\\xc0\\x21\')                          | PPP protocol filed length is 1 byte in scapy2.4.4     |
+    +------------------------+---------------------------------+-----------------------------------------------+-------------------------------------------------------+
+    | L2TP                   | L2TP(\'\\x00\\x00\\x00\\x11\')  | L2TP(b\'\\x00\\x00\\x00\\x11\')               | L2TP is byte type in scapy2.4.4                       |
+    +------------------------+---------------------------------+-----------------------------------------------+-------------------------------------------------------+
+    | PFCP                   | N/A                             | PFCP(S=1, seid=1)                             | PFCP is not supported in scapy2.4.3                   |
+    +------------------------+---------------------------------+-----------------------------------------------+-------------------------------------------------------+
+    | GTPPDUSessionContainer | N/A                             | GTPPDUSessionContainer(type=0, P=1, QFI=0x34) | GTPPDUSessionContainer is not supported in scapy2.4.3 |
+    +------------------------+---------------------------------+-----------------------------------------------+-------------------------------------------------------+
+
+BIOS Setting Prerequisite on x86
+--------------------------------
+
+For the majority of platforms, no special BIOS settings for Tester and DUT.
+DPDK prefers devices bound to ``vfio-pci`` kernel module, therefore, `VT-x` and `VT-d` should be enabled.
+
+.. code-block:: console
+
+   Advanced -> Integrated IO Configuration -> Intel(R) VT for Directed I/O <Enabled>
+   Advanced -> Processor Configuration -> Intel(R) Virtualization Technology <Enabled>
+
+DPDK running Prerequisite
+-------------------------
+
+Hugepage support is required for the large memory pool allocation used for packet buffers.
+DPDK performance will be imporved more with 1G page size than 2M, therefore, recommend to use 1G pages for DPDK.
+The following options should be passed to Linux Cmdline:
+
+.. code-block:: console
+
+   hugepagesz=1G hugepages=16 default_hugepagesz=1G
+
+For more detail information of DPDK requirements, please refer to `Data Plane Development Kit Getting Started Guide <http://dpdk.org/doc/guides>`_.
+
+Performance testing requirements
+--------------------------------
+
+DTS supports three kinds of traffic generators: `Scapy`, `TRex` and `Ixia IxExplorer`. Scapy is for functional testing, TRex and `Ixia IxExplorer` are for performance testing. The mechanism in DTS that mananges traffic generators for performance is called `Pktgen`.
+
+`Ixia IxExplorer` is the principal means used to program Ixia hardware and to perform testing on network devices. Ixia is a hardware traffic generator product of `keysight <https://www.keysight.com>`_ company. DTS requires to install TCL (Tool Command Language) package to connect and control `Ixia IxExplorer`:
+
+.. code-block:: console
+
+   apt-get install tcl
+
+`TRex <https://trex-tgn.cisco.com>`_ is an open source software traffic generator fuelled by DPDK. It generates L3-7 traffic and provides in one tool capabilities. DTS requires to install `Trex` and configure it before lunching DTS.
diff --git a/doc/dts_gsg/usr_guide/trex.rst b/doc/dts_gsg/usr_guide/trex.rst
new file mode 100644
index 0000000..e8b1fe9
--- /dev/null
+++ b/doc/dts_gsg/usr_guide/trex.rst
@@ -0,0 +1,377 @@
+Practice with TRex
+==================
+
+Download TREX
+-------------
+TREX should be installed in Tester, it could be downloaded from http://trex-tgn.cisco.com/trex/release/.
+We recommend to use the latest version v2.88.
+
+.. code-block:: console
+
+    wget http://trex-tgn.cisco.com/trex/release/v2.88.tar.gz
+
+To read more about T-Rex stateless mode, read the
+`T-Rex stateless support guide <https://trex-tgn.cisco.com/trex/doc/trex_stateless.html>`__.
+
+Configure TREX
+--------------
+
+Extract the downloaded TREX tarball
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Extract the downloaded TREX file to /opt/trex/::
+
+    root@tester:/opt# mkdir trex
+    root@tester:/opt# cd trex
+    root@tester:/opt/trex# tar -zxvf v2.88.tar.gz
+    v2.88/
+    v2.88/_t-rex-64-debug
+    v2.88/t-rex-64-debug
+    ...
+    v2.88/trex_client_v2.88.tar.gz
+
+Generate Configure File
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+Identify the performance test ports in tester
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+execute the command like below to list the ports::
+
+    root@tester:/opt/trex/v2.88# ./dpdk_setup_ports.py -s
+
+    Network devices using DPDK-compatible driver
+    ============================================
+    <none>
+
+    Network devices using kernel driver
+    ===================================
+    0000:03:00.0 'VMXNET3 Ethernet Controller' if=ens160 drv=vmxnet3 unused=igb_uio,vfio-pci,uio_pci_generic *Active*
+    0000:0b:00.0 'Device 1592' if=ens192f0 drv=ice unused=igb_uio,vfio-pci,uio_pci_generic
+    0000:0b:00.1 'Device 1592' if=ens192f1 drv=ice unused=igb_uio,vfio-pci,uio_pci_generic
+    Other network devices
+    =====================
+    <none>
+
+Generate Configure File
+^^^^^^^^^^^^^^^^^^^^^^^
+Assume that we use 0000:0b:00.0, 0000:0b:00.1 to connect to DUT port.
+And the ports topology as below::
+
+    trex.0 (0b:00.0/40:a6:b7:0b:55:78) <-------> DUT port 0 (05:00.0/b4:96:91:9f:63:68)
+    trex.1 (0b:00.1/40:a6:b7:0b:55:79) <-------> DUT port 1 (05:00.1/b4:96:91:9f:63:69)
+
+We need to generate the trex config file as below::
+
+    root@tester:/opt/v2.88# ./dpdk_setup_ports.py -i
+    By default, IP based configuration file will be created. Do you want to use MAC based config? (y/N)y
+    +----+------+---------+-------------------+--------------------------------------------+---------+----------+----------+
+    | ID | NUMA |   PCI   |        MAC        |                    Name                    | Driver  | Linux IF |  Active  |
+    +====+======+=========+===================+============================================+=========+==========+==========+
+    | 0  | -1   | 03:00.0 | 00:0c:29:29:30:80 | VMXNET3 Ethernet Controller                | vmxnet3 | ens160   | *Active* |
+    +----+------+---------+-------------------+--------------------------------------------+---------+----------+----------+
+    | 1  | -1   | 0b:00.0 | 40:a6:b7:0b:55:78 | Device 1592                                | ice     | ens192f0 |          |
+    +----+------+---------+-------------------+--------------------------------------------+---------+----------+----------+
+    | 2  | -1   | 0b:00.1 | 40:a6:b7:0b:55:79 | Device 1592                                | ice     | ens192f1 |          |
+    +----+------+---------+-------------------+--------------------------------------------+---------+----------+----------+
+    Please choose an even number of interfaces from the list above, either by ID, PCI or Linux IF
+    Stateful will use order of interfaces: Client1 Server1 Client2 Server2 etc. for flows.
+    Stateless can be in any order.
+    Enter list of interfaces separated by space (for example: 1 3) : 1 2
+    For interface 1, assuming loopback to its dual interface 2.
+    Destination MAC is 40:a6:b7:0b:55:79. Change it to MAC of DUT? (y/N).y
+    Please enter a new destination MAC of interface 1: b4:96:91:9f:63:68
+    For interface 2, assuming loopback to its dual interface 1.
+    Destination MAC is 40:a6:b7:0b:55:78. Change it to MAC of DUT? (y/N).y
+    Please enter a new destination MAC of interface 2: b4:96:91:9f:63:69
+    Print preview of generated config? (Y/n)Y
+    ### Config file generated by dpdk_setup_ports.py ###
+
+    - version: 2
+      interfaces: ['0b:00.0', '0b:00.1']
+      port_info:
+          - dest_mac: b4:96:91:9f:63:68
+            src_mac:  40:a6:b7:0b:55:78
+          - dest_mac: b4:96:91:9f:63:69
+            src_mac:  40:a6:b7:0b:55:79
+
+      platform:
+          master_thread_id: 0
+          latency_thread_id: 1
+          dual_if:
+            - socket: 0
+              threads: [2,3,4,5,6,7]
+
+    Save the config to file? (Y/n)Y
+    Default filename is /etc/trex_cfg.yaml
+    Press ENTER to confirm or enter new file:
+    File /etc/trex_cfg.yaml already exist, overwrite? (y/N)Y
+    Saved to /etc/trex_cfg.yaml.
+    root@tester:/opt/trex/v2.88#
+
+We could not modify the DUT mac during the configuration and modify it in the generated file /etc/trex_cfg.yaml.
+
+Modify Configure File
+^^^^^^^^^^^^^^^^^^^^^
+Make sure the DUT mac of the generated TREX file is correct, and add prefix and limit_memory is better::
+
+    root@tester:/opt/trex/v2.88# cat /etc/trex_cfg.yaml
+    ### Config file generated by dpdk_setup_ports.py ###
+
+    - version: 2
+      interfaces: ['0b:00.0', '0b:00.1']
+      prefix: TREX
+      limit_memory: 4096
+      port_info:
+          - dest_mac: b4:96:91:9f:63:68
+            src_mac:  40:a6:b7:0b:55:78
+          - dest_mac: b4:96:91:9f:63:69
+            src_mac:  40:a6:b7:0b:55:79
+
+      platform:
+          master_thread_id: 0
+          latency_thread_id: 1
+          dual_if:
+            - socket: 0
+              threads: [2,3,4,5,6,7]
+
+    root@tester:/opt/trex/v2.88#
+
+Replace system scapy with TREX scapy
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+As the know trex issue -- trex scapy lib will be conflict with scapy installed in OS, we need the replace the scapy
+in system with trex scapy.
+
+#. backup your scapy::
+
+    cp -rf /usr/local/lib/python3.6/dist-packages/scapy /usr/local/lib/python3.6/dist-packages/scapy_backup
+
+#. unify scapy version with trex::
+
+    cp  -rf /opt/trex/v2.88/external_libs/scapy-2.4.3/scapy/ /usr/local/lib/python3.6/dist-packages/scapy
+
+Configure DTS
+--------------
+
+Configure execution.cfg
+~~~~~~~~~~~~~~~~~~~~~~~
+Add the performance test suite and set perf=true::
+
+    root@tester:dts# cat execution.cfg
+    [Execution1]
+    crbs=192.168.1.1
+    drivername=vfio-pci
+    build_type=meson
+    test_suites=
+            tso,
+    targets=
+        x86_64-native-linuxapp-gcc
+    parameters=nic_type=cfg:perf=true
+    root@tester:dts#
+
+Configure conf/crbs.cfg
+~~~~~~~~~~~~~~~~~~~~~~~
+Set the pktgen_group=trex or pktgen_group=TREX, this item is case insensitive::
+
+    root@tester:dts# cat conf/crbs.cfg
+    [192.168.1.1]
+    dut_ip=192.168.1.1
+    dut_user=root
+    dut_passwd=dutpwd
+    os=linux
+    dut_arch=
+    tester_ip=192.168.1.2
+    tester_passwd=testerpwd
+    ixia_group=
+    pktgen_group=trex
+    channels=4
+    bypass_core0=True
+
+Configure conf/ports.cfg
+~~~~~~~~~~~~~~~~~~~~~~~~~
+This configuration is just same with PF function test, so if you have completed some functional test,
+you have no need to modify the conf/ports.cfg, just like below::
+
+    root@tester:dts# cat conf/ports.cfg
+    [192.168.1.1]
+    ports =
+        pci=0000:05:00.0,peer=0000:0b:00.0;
+        pci=0000:05:00.1,peer=0000:0b:00.1;
+
+In addition, it could be configured as below::
+
+    root@tester:dts# cat conf/ports.cfg
+    [192.168.1.1]
+    ports =
+        pci=0000:05:00.0,peer=TREX:0;
+        pci=0000:05:00.1,peer=TREX:1;
+
+We recommend to use the first format configuration, as it has no need to do modification when we do functional test.
+
+Configure conf/pktgen.cfg
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+Fill in the conf/pktgen.cfg with your TREX setting, for the first time, you should set start_trex=yes.
+Set the IP address of the device which you installed TREX into item ‘server=’, it should be the tester IP.
+The configuration should as below::
+
+    root@tester:dts# cat conf/pktgen.cfg
+    [TREX]
+    trex_root_path=/opt/trex/v2.88
+    trex_lib_path=/opt/trex/v2.88/automation/trex_control_plane/interactive
+    config_file=/etc/trex_cfg.yaml
+    server=192.168.1.1
+    pcap_file=/opt/trex/v2.88/stl/sample.pcap
+    core_num=4
+    #core_mask=0x3
+    ip_src=16.0.0.1
+    ip_dst=10.0.0.1
+    warmup=15
+    duration=-1
+    start_trex=yes
+
+As the trex_lib_path may be different in different versions, you could find the correct path as blow command::
+
+    root@tester:/opt/trex/v2.88# find . -name trex_stl_lib
+    ./automation/trex_control_plane/interactive/trex_stl_lib
+    root@tester:/opt/trex/v2.88#
+
+
+Run DTS performance test with TREX
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Now you can start DTS performance test with TREX::
+
+    root@tester:/home/zhaohy/dts# ./dts
+                           dts:
+    DUT 192.168.1.1
+                        tester: ssh root@192.168.1.1
+    ...
+    pktgen: ssh root@192.168.1.1
+    pktgen: cd /opt/trex/v2.88;./t-rex-64 -i --cfg /etc/trex_cfg.yaml -c 4
+                        pktgen: Starting Scapy server..... Scapy server is started
+    Trying to bind to igb_uio ...
+    /usr/bin/python3 dpdk_nic_bind.py --bind=igb_uio 0000:0b:00.0 0000:0b:00.1
+    ...
+                     TestTSO: Test Case test_perf_TSO_2ports Begin
+             dut.10.240.183.72:
+                        tester:
+                       TestTSO: Executing PMD using 1S/1C/2T
+             dut.10.240.183.72: x86_64-native-linuxapp-gcc/app/dpdk-testpmd  -l 1,45 -n 4 -a 0000:05:00.0 -a 0000:05:00.1  --file-prefix=dpdk_31529_20210324143008   -- -i --rxd=512 --txd=512 --burst=32 --rxfreet=64 --mbcache=128 --portmask=0x3 --max-pkt-len=9000 --txpt=36 --txht=0 --txwt=0 --txfreet=32 --txrst=32
+             dut.10.240.183.72: EAL: Detected 88 lcore(s)
+             ...
+    pktgen: Rx Port 0 stats:
+    rx_port: 0,  rx_bps: 25354096640.000000, rx_pps: 1239130.250000
+                        pktgen: throughput: pps_rx 5463897.750000, bps_rx 50961129472.000000
+                        pktgen: traffic completed.
+    ...
+                       TestTSO:
+    +------------+---------------+------------+
+    | Frame Size | 1S/1C/2T Mpps | % linerate |
+    +============+===============+============+
+    | 128        | 5.371         | 4          |
+    +------------+---------------+------------+
+    | 2500       | 5.464         | 56         |
+    +------------+---------------+------------+
+                           TestTSO: Test Case test_perf_TSO_2ports Result PASSED
+
+FAQ
+---
+
+dpdk hugepage management conflict issue
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+trex use older dpdk version than we release cycle source code. When dpdk change
+the memory management merchanism, trex will meet the following issue.
+
+Trex should run on an independent platform. DUT/Trex should run on two platforms:
+
+* one is used as TESTER and trex server, another one is used as DUT.(dts/pktgen)
+* one is used as trex server, another one is used as DUT/TESTER.(recommended scheme)
+  This scheme can make sure that trex run on its full status capability.
+
+When trex run with dts on the same platform, trex server sometimes boot up
+failed for hugepage error.
+
+.. code-block:: console
+
+      ./t-rex-64  -i --stl -k 4
+
+         Starting Scapy server..... Scapy server is started
+         Trying to bind to igb_uio ...
+         /usr/bin/python3 dpdk_nic_bind.py --bind=igb_uio 0000:85:00.0 0000:8a:00.1
+         The ports are bound/configured.
+         Starting  TRex v2.41 please wait  ...
+         EAL: Can only reserve 1766 pages from 4096 requested
+         Current CONFIG_RTE_MAX_MEMSEG=256 is not enough
+         Please either increase it or request less amount of memory.
+         EAL: FATAL: Cannot init memory
+
+         EAL: Cannot init memory
+
+          You might need to run ./trex-cfg  once
+         EAL: Error - exiting with code: 1
+           Cause: Invalid EAL arguments
+
+trex quit when using Niantic
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+when bind dut NNT port to igb_uio, peer port will get a link down status, then
+trex server using NNT nic will quit.
+
+.. code-block:: console
+
+   WATCHDOG: task 'master' has not responded for more than 2.00044 seconds - timeout is 2 seconds
+
+   *** traceback follows ***
+
+   1       0x55a7c779561a ./_t-rex-64(+0x12761a) [0x55a7c779561a]
+   2       0x7f23da4be1b0 /lib64/libpthread.so.0(+0x121b0) [0x7f23da4be1b0]
+   3       0x55a7c7942d40 rte_delay_us_block + 128
+   4       0x55a7c798d731 ixgbe_setup_mac_link_multispeed_fiber + 337
+   5       0x55a7c79a8f14 ./_t-rex-64(+0x33af14) [0x55a7c79a8f14]
+   6       0x55a7c7954c72 rte_eth_link_get_nowait + 114
+   7       0x55a7c776a988 DpdkTRexPortAttr::update_link_status_nowait() + 24
+   8       0x55a7c77856a6 CGlobalTRex::handle_slow_path() + 118
+   9       0x55a7c7785ad7 CGlobalTRex::run_in_master() + 759
+   10      0x55a7c7785e3c ./_t-rex-64(+0x117e3c) [0x55a7c7785e3c]
+   11      0x55a7c793efba rte_eal_mp_remote_launch + 346
+   12      0x55a7c7789e1e main_test(int, char**) + 1038
+   13      0x7f23d9417f2a __libc_start_main + 234
+   14      0x55a7c7719b9d ./_t-rex-64(+0xabb9d) [0x55a7c7719b9d]
+
+
+   *** addr2line information follows ***
+
+   ??:0
+   ??:0
+   ??:0
+   ??:0
+   ??:0
+   ??:0
+   ??:0
+   ??:0
+   ??:0
+   ??:0
+   ??:0
+   ??:0
+   ??:0
+   ??:0
+
+
+   ./t-rex-64: line 80: 25870 Aborted                 (core dumped) ./_$(
+
+other issues
+~~~~~~~~~~~~
+
+#. linux kernel version should not be too low.
+
+#. Trex only works with even number link peers.
+
+#. Trex only works with nics, which are using the same driver.
+
+#. Before boot up trex, please make sure the peer ports are on up status.
+
+#. If you have ran dpdk on the platform which you want to deploy trex-server,
+   reboot the platform to make sure that trex-server can work fine.
+
+#. If using i40e driver, Trex v2.41 version need i40e nic firmware version newer than 5.02.
+
+#. trex will drop the received packet, which dst mac is the port mac address.
diff --git a/doc/dts_gsg/usr_guide/usage.rst b/doc/dts_gsg/usr_guide/usage.rst
new file mode 100644
index 0000000..ef729a9
--- /dev/null
+++ b/doc/dts_gsg/usr_guide/usage.rst
@@ -0,0 +1,350 @@
+Usage
+=====
+
+Configuration
+-------------
+
+Configuring your own execution file
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+First of all, you must configure execution.cfg as below:
+
+.. code-block:: console
+
+   [Execution1]
+   crbs=<CRB IP Address>
+   drivername=vfio-pci
+   build_type=meson
+   rx_mode=avx512
+   test_suites=
+       hello_world,
+   targets=
+       x86_64-native-linuxapp-gcc
+   parameters=nic_type=cfg:func=true
+
+* crbs: IP address of the DUT. The detail information is defined in file conf/crbs.cfg.
+* drivername: the driver devices used by DPDK bound to.
+* build_type: the tool for building DPDK, it can be meson and makefile. DPDK 20.11+ only uses meson and ninja.
+* rx_mode: vector instructions used in tests, it can be novector/sse/avx2/avx512. it is optional, if not set, dpdk uses avx2 by default.
+* test_suites: test suites and cases that to be executed. use ``:`` to separate suite and it's cases and use ``\`` to separate different cases.
+* targets: DPDK targets to be tested.
+* parameters: multiple keywords as following:
+
+  * nic_type: it is the type of the NIC to use. The types are defined in the file settings.py.
+    There's a special type named as **cfg**, which mean network information will be loaded from file conf/ports.cfg.
+    If use NIC type such as niantic, fortville_25g, it requires all DUT are the same types and no any same devices connected to Tester,
+    as DTS will test all devices connected to Tester. Therefore, recommend using **cfg**.
+  * func=true: run only functional test.
+  * perf=true: run only performance test.
+
+.. note::
+
+   The two options ``func=true`` and ``perf=true`` are mutually exclusive, as the traffic generators for functional and performance are mutually exclusive.
+
+Here are an example for functional testing:
+
+.. code-block:: console
+
+   [Execution1]
+   crbs=192.168.1.1
+   drivername=vfio-pci
+   build_type=meson
+   test_suites=
+        unit_tests_eal:test_version\test_common,
+   targets=
+        x86_64-default-linuxapp-gcc,
+   parameters=nic_type=cfg:func=true
+
+
+Configure CRB information
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Then please add the detail information about your CRB in conf/crbs.conf as following:
+
+.. code-block:: console
+
+   [DUT IP]
+   dut_ip=xxx.xxx.xxx.xxx
+   dut_user=root
+   dut_passwd=
+   os=linux
+   dut_arch=
+   tester_ip=xxx.xxx.xxx.xxx
+   tester_passwd=
+   pktgen_group=
+   channels=4
+   bypass_core0=True
+   dut_cores=
+
+* DUT IP: section name, same as ``crbs`` in execution.cfg.
+* dut_ip: IP address of the DUT, same as ``crbs`` in execution.cfg.
+* dut_user: User name of DUT linux account
+* dut_passwd: Password of DUT linux account
+* tester_ip: IP address of tester
+* tester_passwd: Password of Tester linux account, user name should same as dut_user
+* pktgen_group: traffic generator name, it can be ``trex`` or ``ixia``, it is optional, if not set, DTS can't do performance tests.
+* channels: number of memory channels for DPDK EAL
+* bypass_core0: skip the first core when initialize DPDK
+* dut_cores: DUT core list, eg: 1,2,3,4,5,18-22, it is optional, if it is ``None`` or not set, all core list will be used.
+
+Here are an example for functional testing:
+
+.. code-block:: console
+
+   [192.168.1.1]
+   dut_ip=192.168.1.1
+   dut_user=root
+   dut_passwd=dutpasswd
+   os=linux
+   tester_ip=192.168.1.2
+   tester_passwd=testerpasswd
+   channels=4
+   bypass_core0=True
+
+
+Configure port information
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+If set ``nic_type=cfg`` in execution.cfg, please add port configuration in conf/ports.cfg as following:
+
+.. code-block:: console
+
+   [DUT IP]
+   ports =
+       pci=<Pci BDF>,peer=<Pci BDF>;
+       pci=<Pci BDF>,peer=IXIA:X.Y;
+       pci=<Pci BDF>,peer=TREX:X;
+
+It supports three patterns, the first one is for functional testing, the second one is for ``IXIA``, the third one is for ``TRex``:
+
+* pci: Device pci address of DUT
+* peer: info of Tester port which connected to the DUT device:
+
+  * if it is func testing, it is pci address
+  * if pktgen is ``TRex``, the `X` in ``TREX:X`` is port id in TRex configuration file, e.g. /etc/trex_cfg.yaml.
+  * if pktgen is ``IXIA``, the `X` is card id ,and the `Y` is port id, which configured in ./conf/pktgen.cfg.
+
+Here are an example for functional testing:
+
+.. code-block:: console
+
+   [192.168.1.1]
+   ports =
+       pci=0000:06:00.0,peer=0000:81:00.0;
+       pci=0000:06:00.1,peer=0000:81:00.1;
+
+Here are an example for IXIA:
+
+.. code-block:: console
+
+   [192.168.1.1]
+   ports =
+       pci=0000:18:00.0,peer=IXIA:1.1;
+       pci=0000:18:00.1,peer=IXIA:1.2;
+
+Here are an example for TRex:
+
+.. code-block:: console
+
+   [192.168.1.1]
+   ports =
+       pci=0000:18:00.0,peer=TREX:1;
+       pci=0000:18:00.1,peer=TREX:1;
+
+
+Configure all test suites
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+conf/global_suite.cfg is a global suite configure file which is shared by all suites.
+
+.. code-block:: console
+
+    [global]
+    vf_driver=vfio-pci
+
+* vf_driver: VF driver that for VF testing, recommend keep the default value ``vfio-pci``.
+
+
+Configure your own suites
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Not all test suites have it's own configuration file which depended on script. If it has, the configuration file is conf/[suite_name].cfg
+For example, suite metrics has its suite configure file conf/metric.cfg:
+
+.. code-block:: console
+
+    [suite]
+    frames_cfg = { 64: 0.07, 128: 0.04, 256: 0.02, 512: 0.01, 1024: 0.01 }
+    duration = 60
+    sample_number = 3
+    rates = [100, 80, 40, 20]
+
+
+Configure your pktgen
+~~~~~~~~~~~~~~~~~~~~~
+
+Pktgen information are configured in conf/pktgen.cfg, pktgen_group must be configured too:
+
+* traffic generator is ``TRex``, set ``pktgen_group=trex`` in crbs.cfg.
+* traffic generator is ``IXIA``, set ``pktgen_group=ixia`` in crbs.cfg.
+
+Then configure conf/pktgen.cfg as following:
+
+.. code-block:: console
+
+   [TREX]
+   trex_root_path=/opt/trex/v2.84/
+   trex_lib_path=/opt/trex/v2.84/automation/trex_control_plane/interactive
+   config_file=/etc/trex_cfg.yaml
+   server=192.168.1.1 # equal to tester IP, TREX should be installed in tester
+   pcap_file=/opt/trex/v2.84/stl/sample.pacp
+   core_num=16
+   ip_src=16.0.0.1
+   ip_dst=10.0.0.1
+   warmup=15
+   duration=-1
+   start_trex=yes
+
+   [IXIA]
+   ixia_version=6.62
+   ixia_ip=xxx.xxx.xxx.xxx
+   ixia_ports=
+       card=1,port=1;
+       card=1,port=2;
+       card=1,port=3;
+       card=1,port=4;
+
+* TREX: section name for TRex.
+* trex_root_path: source code path for TRex
+* trex_lib_path: the director where dts can import Trex API
+* start_trex: whether DTS start TRex server, suggest 'yes' for one-time test, and 'no' for CI integration
+
+* IXIA: section name for IXIA.
+* ixia_version: the version of IxExplorer.
+* ixia_ip: IP of ixia
+* ixia_ports: ixia ports connected to DUT.
+
+Here are an example for TRex:
+
+.. code-block:: console
+
+   [TREX]
+   trex_root_path=/opt/trex/v2.84/
+   trex_lib_path=/opt/trex/v2.84/automation/trex_control_plane/interactive
+   config_file=/etc/trex_cfg.yaml
+   server=192.168.1.1 # equal to tester IP, TREX should be installed in tester
+   pcap_file=/opt/trex/v2.84/stl/sample.pacp
+   core_num=16
+   ip_src=16.0.0.1
+   ip_dst=10.0.0.1
+   warmup=15
+   duration=-1
+   start_trex=yes
+
+Here are an example for IXIA:
+
+.. code-block:: console
+
+   [IXIA]
+   ixia_version=9.00
+   ixia_ip=192.168.2.1
+   ixia_ports=
+       card=3,port=1;
+       card=3,port=2;
+   ixia_force100g=disable
+
+
+Running the Application
+-----------------------
+
+DTS supports multiple parameters which will select different of working mode of test framework.
+In the meantime, DTS can work with none parameter, then every parameter will set to its default value:
+
+.. code-block:: console
+
+   usage: main.py [-h] [--config-file CONFIG_FILE] [--snapshot SNAPSHOT] [--output OUTPUT] [-s]
+                  [-t TEST_CASES] [-d DIR] [-v] [--debug] [--debugcase] [--re_run RE_RUN]
+                  [--commands COMMANDS] [--update-expected]
+
+DTS supports the following parameters:
+
+*   ``-h, --help``
+
+    Display a help message and quit.
+
+*   ``--config-file CONFIG_FILE``
+
+    Execution file which contains test suites, DPDK target information and so on.
+    The default value is `execution.cfg`.
+
+*   ``--snapshot SNAPSHOT``
+
+    Snapshot .tgz file to use as input。
+    The deault value is `./dep/dpdk.tar.gz`.
+
+*   ``--output OUTPUT``
+
+    Output directory where dts log and result saved.
+    The default value is `./output`.
+
+*   ``-s, --skip-setup``
+
+    Skip all possible setup steps done on both DUT and tester.
+
+*   ``-t TEST_CASES, --test-cases TEST_CASES``
+
+    Execute only the specific test cases.
+    The default value is all test cases.
+
+*   ``-d DIR``
+
+    Output directory where dpdk package is extracted.
+
+*   ``-v, --verbose``
+
+    Enable verbose output, all message output on screen.
+
+*   ``--debug``
+
+    Enable debug mode, user can enter debug mode in process with `ctrl+c`
+    User can do further debug by attached to sessions or call pdb module by interact interface:
+
+.. code-block:: console
+
+   help(): show help message
+   list(): list all connected sessions
+   connect(name): connect to session directly
+   exit(): exit dts
+   quit(): quit debug mode and into normal mode
+   debug(): call python debug module
+
+*   ``--debugcase``
+
+   Enable debug mode with test cases.
+   DTS will hang and wait for user command before executing each test case:
+
+.. code-block:: console
+
+   rerun(): rerun current case
+   ctrl + d: exit current case
+
+*   ``--re_run RE_RUN``
+
+    Times that will re-run when case failed.
+    The default value is 0, and it must be >=0.
+
+*   ``--update-expected``
+
+    Enable write-back expected value of performance.
+    It requires test scripts support.
+
+Here are examples:
+
+.. code-block:: console
+
+   ./dts
+   ./dts -s
+   ./dts -s -d /home/dpdk
+   ./dts --debug
+   ./dts --debug --debugcase
+   ./dts --output test1
diff --git a/doc/dts_gsg/virtualization.rst b/doc/dts_gsg/virtualization.rst
deleted file mode 100755
index 15d7967..0000000
--- a/doc/dts_gsg/virtualization.rst
+++ /dev/null
@@ -1,617 +0,0 @@
-Virtualization Framework
-========================
-
-Design Concept
---------------
-DTS virtualization framework is based on extendible design which can support different types of hypervisors and their parameters. 
-
-Suite for virtual feature should handle virtual machine creation and destruction. It only need to execute some most basic operations on guest like start, stop. There're two ways to configure virtual machine. One is configuration file, the other one is to call hypervisor internal API. Suite can choose anyway of them based on its implementation.
-
-.. note::
-	If VM configurations are different between test cases, those configurations shared with all cases should be defined in suite local configuration file. Those dynamical configurations should be set by hypervisor module's API.
-
-Virtual machine DUT class is inherited from host DUT class. This mean that for vm DUT, can call the same API as DUT object.
-
-Flow Chart
-~~~~~~~~~~
-
-Below picture show the virtualization related modules working flow. 
-
-.. figure:: image/virt_flow.svg
-
-System Requirements
--------------------
-
-Host Preparation
-~~~~~~~~~~~~~~~~
-
-Kernel should enable KVM. In bios feature Intel(R) Virtualization Technology should be enabled. Emulator qemu must be installed in host.
-
-.. note::
-	Some features like virtio cuse request higher version than default qemu release with linux distribution. For those features, qemu should be updated to version later than 2.1.
-
-
-Guest Preparation
-~~~~~~~~~~~~~~~~~
-
-SSH connection
-""""""""""""""
-
-DTS create ssh connection to guest based on redirect guest ssh port to host port. Ssh connection will require one interface in guest which can connect to host. User should setup one default interface (e1000) in guest and make sure it can be up after guest boot up. 
-
-.. note::
-	Qemu process contained with one virtual DHCP server on 10.0.2.2 and will be allocated an address starting from 10.0.2.15. For more information about qemu network, please reference to https://en.wikibooks.org/wiki/QEMU/Networking.
-
-
-In qemu module, the default e1000 device's pci address is assigned to 00:1f.0 which is the very end of guest pci address. In guest, we configure udev rule and assign the default interface named as "host_connect".
-
-Add udev rule for default e1000 device:
-
-.. code-block:: console
-
-    vim /etc/udev/rules.d/70-persistent-net.rules
-    KERNELS=="0000:00:1f.0",SUBSYSTEMS=="pci", ACTION=="add", DRIVERS=="?*" ,KERNEL=="eth*", NAME="host_connect"
-
-Enable dhcp on default host_connect interface.
-
-.. code-block:: console
-
-    vim /etc/sysconfig/network-scripts/ifcfg-host_connect
-    	TYPE="Ethernet"
-    	BOOTPROTO="dhcp"
-    	DEFROUTE="yes"
-    	DEVICE="host_connect"
-    	NAME="host_connect"
-    	ONBOOT="yes"
-    	PEERDNS="yes"
-    	PEERROUTES="yes"
-    	IPV6_PEERDNS="yes"
-    	IPV6_PEERROUTES="yes"
-
-.. code-block:: console
-
-    chkconfig --level 2345 network on
-
-For network access, should disable guest firewall service.
-
-.. code-block:: console
-
-    systemctl disable firewalld.service
-
-QGA connection
-""""""""""""""
-
-Install qemu guest agent, DTS will manage virtual machine through QGA if control type is 'qga'.
-
-.. code-block:: console
-
-    yum install qemu-guest-agent.x86_64
-
-Console connection
-""""""""""""""""""
-
-Enable virtual machine serial console in kernel command line, DTS will manage virtual machine through serial port if control type is 'telnet' or 'socket'.
-
-.. code-block:: console
-
-   console=ttyS0,115200
-
-Suite Programing
-----------------
-
-Add Configuration File
-~~~~~~~~~~~~~~~~~~~~~~
-
-Configuration file should be placed in conf/{suite_name}.cfg and in test suite this file will be loaded for VM configurations. Below is one sample for virtualization suite configuration file.
-
-The section name between [] is the VM name. Here we changed default cpu, mem, disk, UEFI configurations. And add two local configurations login and vnc into configuration file.
-For cpu parameter, we changed core number to 2 and pin these two cores to socket 1 cores for performance concern. For mem parameter, we changed guest using with hugepage backend memory. It also concerned about performance. For disk parameter, we should change it local disk image absolute path.
-For pflash parameter, we changed UEFI CODE and UEFI VARs file, which you specified when you created the VM.
-
-Login parameter should be added when guest login username and password not same as host. VNC parameter should be added when need debug guest with vnc display. 
-
-.. code-block:: console
-
-    # vm configuration for vhost sample case
-    [vm0]
-    cpu =
-       model=host,number=2,cpupin=24 25;
-    mem =
-        size=4096,hugepage=yes;
-    disk =
-        file=/home/img/vm0.img,opt_format=raw,opt_if=virtio,opt_index=0,opt_media=disk;
-    pflash =
-        file=/home/img/flash_code.img;
-        file=/home/img/flash_vars.img;
-    login =
-        user=root,password=tester;
-    vnc =
-        displayNum=1;
-
-	
-Add Parameters
-~~~~~~~~~~~~~~
-Below is the brief view of the qemu parameters of vxlan sample virtual machine. These parameters are gathered into one list of python dictionary.
-
-.. code-block:: console
-
-    [{'name': [{'name': 'vm0'}]}, 
-    {'enable_kvm': [{'enable': 'yes'}]}, 
-    {'control': [{'type': 'telnet'}]},
-    {'daemon': [{'enable': 'yes'}]}, 
-    {'monitor': [{'path': '/tmp/vm0_monitor.sock'}]},
-    {'net': [{'opt_addr': '1f', 'type': 'nic', 'opt_vlan': '0'}, {'type': 'user', 'opt_vlan': '0'}]},
-    {'device': [{'opt_mac': '00:00:20:00:00:20', 'opt_path': './vhost-net', 'driver': 'vhost-user'}, {'opt_mac': '00:00:20:00:00:21', 'opt_path': './vhost-net', 'driver': 'vhost-user'}]},
-    {'cpu': [{'model': 'host', 'number': '4', 'cpupin': '24 25 26 27'}]},
-    {'mem': [{'hugepage': 'yes', 'size': '4096'}]},
-    {'disk': [{'file': '/storage/vm-image/vm0.img', 'opt_format': 'raw', 'opt_if': 'virtio', 'opt_index': '0', 'opt_media': 'disk'}]},
-    {'pflash': [{'file': '/storage/vm-image/flash_code.img'}]},
-    {'pflash': [{'file': '/storage/vm-image/flash_vars.img'}]},
-    {'login': [{'password': 'tester', 'user': 'root'}]},
-    {'vnc': [{'displayNum': '1'}]}]
-
-
-In vxlan sample suite, we need to support socket based vhost-user network devices. Qemu command for vhost-user device will like as below. 
-	
-.. code-block:: console
-
-    -chardev socket,path=/path/to/socket,id=chr0 \
-    -netdev type=vhost-user,id=net0,chardev=chr0 \	
-    -device virtio-net-pci,netdev=net0,mac=00:00:20:00:00:20
-
-For user configuration, we should only care about socket path and mac address. Configuration of vhost-user device should like below.
-
-.. code-block:: console
-
-    device = 
-    	    driver=vhost-user,opt_path=./vhost-net,opt_mac=00:00:20:00:00:20
-            driver=vhost-user,opt_path=./vhost-net,opt_mac=00:00:20:00:00:21
-
-Python code should like below, vxlan_sample suite chosen this way.
-
-.. code-block:: console
-
-    vm_params = {}
-    vm_params['driver'] = 'vhost-user'
-    vm_params['opt_path'] = './vhost-net'
-    vm_params['opt_mac'] = "00:00:20:00:00:20"
-    self.vm.set_vm_device(**vm_params)
-    vm_params['opt_mac'] = "00:00:20:00:00:21"
-    self.vm.set_vm_device(**vm_params)
-
-If parameter is device, function add_vm_{device} will be called and device options will passed as arguments. The options will be formatted into python dictionary.
-
-.. code-block:: console
-
-    {'opt_mac': '00:00:20:00:00:20', 'opt_path': './vhost-net', 'driver': 'vhost-user'}
-    
-    def add_vm_device(self, **options):
-        if options['driver'] == 'vhost-user':
-            self.__add_vm_virtio_user_pci(**options)
-    
-
-In internal add virtio user device function, qemu module will generate chardev, netdev and virtio-net-pci command line in sequence.
-
-.. code-block:: console
-
-    def __add_vm_virtio_user_pci(self, **options):
-    if 'opt_path' in options.keys() and options['opt_path']:
-    	# add socket char device command line
-            dev_boot_line = '-chardev socket'
-    	char_id = 'char%d' % self.char_idx
-    	dev_boot_line += separator + 'id=%s' % char_id + separator + 'path=%s' % 	options['opt_path']
-    	self.char_idx += 1
-    	self.__add_boot_line(dev_boot_line)
-    
-    	# add netdev command line
-    	netdev_id = 'netdev%d' % self.netdev_idx
-    	self.netdev_idx += 1
-    	dev_boot_line = '-netdev type=vhost-user,id=%s,chardev=%s,vhostforce' % 	(netdev_id, char_id)
-    	self.__add_boot_line(dev_boot_line)
-    	
-    	# add virtio-net-pci command line
-    	opts = {'opt_netdev': '%s' % netdev_id}
-            if 'opt_mac' in options.keys() and \
-                options['opt_mac']:
-            opts['opt_mac'] = options['opt_mac']
-                self.__add_vm_virtio_net_pci(**opts)
-
-			
-VM Management
-~~~~~~~~~~~~~
-
-Suite should have known that which hypervisor type based on. With virtual machine instance, suite can start, stop and check status of the guest. All infrastructures required have been made up by virtualization module, suite should not handle that.
- 
-.. note::
-	Test case should focus in feature validation. VM management related codes recommended to be placed in set_up_all or set_up functions.
-
-
-In vxlan sample suite, all test cases request to restart virtual machine. The backend application will be started with different parameters. So VM start up code is placed in set_up function.
-
-.. code-block:: console
-
-    def set_up(self):
-        """
-        Run before each test case.
-        """ 
-        tep_cmd = tep_cmd_temp % {
-            'COREMASK': self.coremask,
-            'CHANNELS': self.dut.get_memory_channels(),
-            'VXLAN_PORT': self.vxlan_port, 'NB_DEVS': vm_num * 2,
-            'FILTERS': self.OUTER_INNER_VNI, 'TX_CHKS': chksum,
-            'ENCAP': encap, 'DECAP': decap}
-    	self.prepare_vxlan_sample_env(tep_cmd)
-
-Before VM operations, vxlan sample feature request to start tep_termination application first. To initialized hypervisor kvm instance, there're three parameters required. The first is DUT object, the second is VM name and the third is suite name.
-
-.. code-block:: console
-
-    def prepare_vxlan_sample_env(self, tep_cmd):
-        # remove unexpected socket
-        self.dut.send_expect("rm -rf vhost-net", "# ")
-    
-        # start tep_termination first
-        self.dut.send_expect(tep_cmd, "VHOST_CONFIG: bind to vhost-net")
-    
-        # start one vm
-        self.vm = QEMUKvm(self.dut, 'vm0', 'vxlan_sample')
-
-Before VM start up, suite still can change VM parameters and in this case suite will add two vhost-user devices.
-
-.. code-block:: console
-
-    # add two virtio user netdevices
-    vm_params = {}
-    vm_params['driver'] = 'vhost-user'
-    vm_params['opt_path'] = './vhost-net'
-    vm_params['opt_mac'] = "00:00:20:00:00:20"
-    self.vm.set_vm_device(**vm_params)
-    vm_params['opt_mac'] = "00:00:20:00:00:21"
-    self.vm.set_vm_device(**vm_params)
-
-Add exception handler in VM start, it is critical function and better to handle the exception.
-
-.. code-block:: console
-
-    try:
-        self.vm_dut = self.vm.start()
-        if self.vm_dut is None:
-            raise Exception("Set up VM ENV failed!")
-    except Exception as e:
-        print dts.RED("Failure for %s" % str(e))
-
-	return True
-
-VM start function will just return VM DUT object and support all DUT APIs.
-
-.. code-block:: console
-
-    def vm_testpmd_start(self, vm_id=0):
-        """
-        Start testpmd in virtual machine
-        """
-        if vm_id == 0 and self.vm_dut is not None:
-            # start testpmd
-            self.vm_dut.send_expect(self.vm_testpmd, "testpmd>", 20)
-            # set fwd mac
-            self.vm_dut.send_expect("set fwd io", "testpmd>")
-            # start tx_first
-            self.vm_dut.send_expect("start tx_first", "testpmd>")
-
-When case has been run, need kill guest dpdk application and stop VM. 
-
-.. code-block:: console
-
-    def clear_vxlan_sample_env(self):
-        if self.vm_dut:
-            self.vm_dut.kill_all()
-            time.sleep(1)
-    
-        if self.vm:
-            self.vm.stop()
-            self.vm = None
-
-KVM Module
-----------
-
-Default Parameters
-~~~~~~~~~~~~~~~~~~
-
-Enable KVM
-""""""""""
-
-DTS enable KVM full virtualization support as default. This option will significant improve the speed of virtual machine.
-
-Control (Qemu Guest Agent)
-"""""""""""""""""""""""""""
-
-Qemu monitor supply one method to interact with qemu process. DTS can monitor guest status by command supplied by qemu guest agent. Qemu guest agent is based on virtio-serial devices.
-
-.. code-block:: console
-
-    -device virtio-serial -device virtserialport,chardev=vm_qga0,name=org.qemu.guest_agent.0
-    -daemonize -monitor unix:/tmp/vm_monitor.sock,server,nowait
-
-Check whether guest os has been started up.
-
-.. code-block:: console
-
-    qemu-ga-client address=/tmp/{vm_name}_qga0.sock ping 120
-
-.. note::
-
-    We only wait two minutes for guest os start up. For guest os only has few hardware and we has disabled most services, so 2 minutes is enough.
-    This command will be return when guest os is ready, so DTS will not wait 2 minutes for each time.
-
-Check whether guest os default interface has been up.
-
-.. code-block:: console
-
-    qemu-ga-client address=/tmp/{vm_name}_qga0.sock ifconfig
-
-DTS will wait for guest os default interface upped and get auto dhcp address. After that DTS can connect to guest by ssh connections.
-
-.. code-block:: console
-
-    lo:
-         inet 127.0.0.1  netmask 255.0.0.0
-            inet6 ::1  prefixlen 128
-    host_connect:
-            inet 10.0.2.15  netmask 255.255.255.0
-            inet6 fe80::200:ff:feb9:fed7  prefixlen 64
-            ether 00:00:00:b9:fe:d7
-
-Power down  guest os.
-
-.. code-block:: console
-
-    qemu-ga-client address=/tmp/{vm_name}_qga0.sock powerdown
-
-.. note::
-
-    For more information about qemu guest agent, please refer to https://wiki.qemu.org/Features/GuestAgent.
-
-Control (Qemu Serial Port)
-""""""""""""""""""""""""""
-
-Qemu serial port is the default method to interact with guest OS. DTS can monitor guest status/manage guest network by serial port.
-
-.. code-block:: console
-
-    -serial telnet::7000,server,nowait
-
-DTS will check the output from serial port and determine whether guest os has been started up. The prompt string for guest login session can be configured by parameter "start".
-
-.. code-block:: console
-
-    start =
-        wait_seconds=120,login_timeout=60,login_prompt=login:,password_prompt=Password:;
-
-.. note::	
-
-	Default timeout for guest OS start up is 2 minutes. For guest os only has few hardware and we has disabled most services, so 2 minutes is enough. If guest OS can't start up in 2 minutes, DTS will try to restart it once.
-
-DTS will check default interface upped and utilize dhcp to retrieve address. After that DTS can connect to guest by ssh connections.
-
-.. code-block:: console
-
-	lo:
-		 inet 127.0.0.1  netmask 255.0.0.0
-			inet6 ::1  prefixlen 128
-	host_connect:
-			inet 10.0.2.15  netmask 255.255.255.0
-			inet6 fe80::200:ff:feb9:fed7  prefixlen 64
-			ether 00:00:00:b9:fe:d7
-
-Power down guest os by serial port.
-
-.. code-block:: console
-
-    init 0
-	
-.. note::
-
-	For more information about qemu serial port, please reference to https://qemu.weilnetz.de/doc/qemu-doc.html.
-	
-Qemu Monitor
-""""""""""""
-
-After guest started, there's no way to known that host pci devices assigned-into guest.
-When assign host pci device into guest, we also add "id" string for this device.
-
-.. code-block:: console
-
-	-device pci-assign,host=07:10.0,id=pt_0
-	
-With this command, we assign host VF device 07:10.0 into guest and it is named as "pt_0". "pt_0" means it's the first device pass through into guest os.
-After guest os started, we use the QEMU/Monitor "info pci" command to dump PCI information and generate guest and host pci mapping by "id".
-
-.. code-block:: console
-
-	Bus  0, device   4, function 0:
-		Ethernet controller: PCI device 8086:10ed
-		  BAR0: 64 bit memory at 0xfebb0000 [0xfebb3fff].
-		  BAR3: 64 bit memory at 0xfebb4000 [0xfebb7fff].
-		  id "pt_0"
-	Bus  0, device   5, function 0:
-		Ethernet controller: PCI device 8086:10ed
-		  BAR0: 64 bit memory at 0xfebb8000 [0xfebbbfff].
-		  BAR3: 64 bit memory at 0xfebbc000 [0xfebbffff].
-		  id "pt_1"
-
-Connection to monitor socket on DUT.
-
-.. code-block:: console
-
-	nc -U /tmp/{vm_name}_monitor.sock
-
-.. note::
-
-    For More detail information about qemu monitor. https://en.wikibooks.org/wiki/QEMU/Monitor#info
-
-Qemu Machine (Aarch64)
-""""""""""""""""""""""
-
-DTS need set default qemu machine type as virt for Aarch64. This option is mandatory for qemu-system-aarch64.
-
-Configured Parameters
-~~~~~~~~~~~~~~~~~~~~~
-
-Net
-"""
-
-Net parameter is used to create one new Network Interface. There're few types of network interface supported by net parameter.
-
-Type supported:
-    nic: Network Interface Card
-    user: connect the user mode network stack
-    tap: connect the host TAP network interface
-    bridge: connects a host TAP network interface to a host bridge device 
-
-Each type has different options, detail information shown in below tables.
-
-Options for nic:
-
-.. table::
-
-	+-----------------+----------------------------------+----------------+-----------+
-	| Option of nic	  | Description	                     | Default value  | Must have |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_vlan        | vlan of virtual nic	             | 0              | No        |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_macaddr     | If not assign, nic will generate | N/A            | No        |
-	|                 | random mac	                     | 	              |           |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_model       | model of virtual nic             | e1000	      | No        |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_name        | name be assigned for use in      | N/A            | No        | 
-	|                 | monitor command                  |                |           |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_addr        | pci address in virtual machine   | N/A            | No        |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_vectors     | number v of MSI-X vectors        | N/A            | No        |
-	+-----------------+----------------------------------+----------------+-----------+
-
-Options for user: 
-
-.. table::
-
-	+-----------------+----------------------------------+----------------+-----------+
-	| Option of user  | Description	                     | Default value  | Must have |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_vlan        | vlan of virtual nic	             | 0              | No        |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_hostfwd     | Redirect incoming TCP or UDP     | N/A            | No        |
-	|                 | connections to the host port     |                |           |
-	+-----------------+----------------------------------+----------------+-----------+
-
-Options for tap: 
-
-.. table::
-
-	+-----------------+----------------------------------+----------------+-----------+
-	| Option of tap   | Description	                     | Default value  | Must have |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_vlan        | vlan of virtual nic	             | 0              | No        |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_br          | bridge which tap device bound to | br0            | Yes       |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_script      | script for tap device network    | /etc/qemu-ifup | No        |
-	|                 | configure                        |                |           |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_downscript  | script for tap device network    | /etc/          | No        |
-	|                 | deconfigure	                     | qemu-ifdown    |           |
-	+-----------------+----------------------------------+----------------+-----------+
-
-Device
-""""""
-
-Device parameter is used to add one emulated device into guest. Now DTS support few types of driver based devices.
-
-Driver supported:
-		pci-assign: pci passthrough host devices into vm
-		virtio-net-pci: virtio devices
-		vhost-user: vhost-user network device based on socket
-		vhost-cuse: vhost-user network device based on tap
-
-
-Options for pci-assign:
-
-.. table::
-
-	+-----------------+----------------------------------+----------------+-----------+
-	| Options of      | Description                      | Default value  | Must have |
-	| pci-assign      |                                  |                |           |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_host        | host pci device address          | N/A            | Yes       |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_addr        | pci address in virtual machine   | N/A            | No        |
-	+-----------------+----------------------------------+----------------+-----------+
-
-Options for virtio-net-pci:
-
-.. table::
-
-	+-----------------+----------------------------------+----------------+-----------+
-	| Option of       | Description	                     | Default value  | Must have |
-	| virtio-net-pci  |                                  |                |           |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_netdev      | name for virtio netdev           | N/A            | Yes       |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_id          | netdevice id for virtio          | N/A            | Yes       |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_mac         | mac address on virtio-net device | N/A            | No        |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_bus         | pci bus of virtio-net device in  | N/A            | No        |
-	|                 | vm                               |                |           |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_addr        | pci address of virtio-net-pci    | N/A            | Yes       |
-	|                 | device in vm                     |                |           |
-	+-----------------+----------------------------------+----------------+-----------+
-
-Options for vhost-user:
-
-.. table::
-
-	+-----------------+----------------------------------+----------------+-----------+
-	| Option of       | Description	                     | Default value  | Must have |
-	| vhost-user      |                                  |                |           |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_path        | unix socket path of character    | N/A            | Yes       |
-	|                 | device                           |                |           |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_mac         | mac address on virtio-net-pci    | N/A            | Yes       |
-	|                 | device                           |                |           |
-	+-----------------+----------------------------------+----------------+-----------+
-
-Options for vhost-cuse:
-
-.. table::
-
-	+-----------------+----------------------------------+----------------+-----------+
-	| Option of       | Description	                     | Default value  | Must have |
-	| vhost-cuse      |                                  |                |           |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_mac         | mac address on virtio-net-pci    | N/A            | No        |
-	|                 | device                           |                |           |
-	+-----------------+----------------------------------+----------------+-----------+
-	| opt_settings    | virtio device settings           | N/A            | No        |
-	+-----------------+----------------------------------+----------------+-----------+
-	
-VNC
-"""
-
-Vnc parameter is used for add vnc display in qemu process. There's only one option "displayNum" supported by this parameter. This parameter is added for user debug.
-
-.. note::
-	Display number should be different between virtual machines.
-	
-User Command
-""""""""""""
-
-User command parameter is used for add one special command for qemu. Some qemu command lines are so unique, there's no value to add certain parameter support for them. Those command lines can be implemented by this parameter. 
-
-Login
-"""""
-
-Login parameter is used for specify guest login username and password.
