[dts] [Patch V1] test_plans: add test plan for exception path sample

[Lei <lei.a.yao@intel.com>]

From: Lei Yao <lei.a.yao@intel.com>

This patch will add the test plan for exception path sample. The first
patch will just include the performance test which is based on Ixia
---
 test_plans/exception_path_test_plan.rst | 98 +++++++++++++++++++++++++++++++++
 1 file changed, 98 insertions(+)
 create mode 100644 test_plans/exception_path_test_plan.rst

diff --git a/test_plans/exception_path_test_plan.rst b/test_plans/exception_path_test_plan.rst
new file mode 100644
index 0000000..d951275
--- /dev/null
+++ b/test_plans/exception_path_test_plan.rst
@@ -0,0 +1,98 @@
+.. Copyright (c) <2010-2019>, Intel Corporation
+   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.
+
+================================
+DPDK Exception Path Sample Tests
+================================
+
+Description
+===========
+
+The Exception Path sample application is a simple example that demonstrates 
+the use of the DPDK to set up an exception path for packets to go through 
+the Linux* kernel. This is done by using virtual TAP network interfaces. 
+These can be read from and written to by the DPDK application and appear 
+to the kernel as a standard network interface.
+
+The application creates two threads for each NIC port being used. One thread 
+reads from the port and writes the data unmodified to a thread-specific TAP 
+interface. The second thread reads from a TAP interface and writes the data 
+unmodified to the NIC port.
+
+Prerequisites
+=============
+
+Two NIC ports and Iixa port are needed for this performance test. 
+
+
+Test Case: Exception Path Performance test
+==========================================
+1. Bind two NIC ports to DPDK driver, for example
+   usertools/dpdk-devbind.py --bind=vfio-pci device_bus_id1 device_bus_id2
+
+2. Test Performance with 2 Cores and 1 NIC port. 1 core is for NIC RX side 
+   and another core is for NIX TX side. For example:
+    ./examples/exception_path/build/exception_path -n 4 -c 0x03 -- -p 0x1 -i 0x01 -o 0x02
+
+3. Configure the two TAP interface generated by the exception path sample and 
+   add bridge for packets routing
+   ifconfig tap_dpdk_22 up
+   ifconfig tap_dpdk_23 up
+   brctl addbr "br_dpdk_00"
+   brctl addif br_dpdk_00 tap_dpdk_22
+   brctl addif br_dpdk_00 tap_dpdk_23
+   ifconfig br_dpdk_00 up
+   
+4. From packets generator, send broadcast packets to the NIC and check the 
+   throughput
+   
+5. Similar to Step2~Step4, Test performance with 4 cores and 2 NIC ports. 
+   ./examples/exception_path/build/exception_path -n 4 -c 0x0f -- -p 0x3 -i 0x03 -o 0x0C
+    ifconfig tap_dpdk_22 up
+    ifconfig tap_dpdk_23 up
+    brctl addbr "br_dpdk_00"
+    brctl addif br_dpdk_00 tap_dpdk_22
+    brctl addif br_dpdk_00 tap_dpdk_23
+    ifconfig br_dpdk_00 up
+    ifconfig tap_dpdk_24 up
+    ifconfig tap_dpdk_25 up
+    brctl addbr "br_dpdk_01"
+    brctl addif br_dpdk_01 tap_dpdk_24
+    brctl addif br_dpdk_01 tap_dpdk_25
+    ifconfig br_dpdk_01 up
+
+6.  From packets generator, send broadcast packets to both 2 NICs then check the 
+    aggregated throughput
+   
+   
+
+
-- 
2.7.4