[dts] [PATCH V1] test_plans/efd: test plan revise

[Zhe <zhe.wan@intel.com>]

From: Zhe Wan <zhe.wan@intel.com>

Signed-off-by: Zhe Wan <zhe.wan@intel.com>
---
 test_plans/efd_test_plan.rst | 43 +++++++++++++++++++++++++++++--------------
 1 file changed, 29 insertions(+), 14 deletions(-)

diff --git a/test_plans/efd_test_plan.rst b/test_plans/efd_test_plan.rst
index d6962e7..dfde28a 100644
--- a/test_plans/efd_test_plan.rst
+++ b/test_plans/efd_test_plan.rst
@@ -58,6 +58,9 @@ Two ports connect to packet generator.
 
 DUT board must be two sockets system and each cpu have more than 16 lcores.
 
+Unit test cases
+===================
+
 Test Case: EFD function unit test
 ---------------------------------
 Start test application and run efd unit test::
@@ -77,28 +80,20 @@ Verify when key size increased, no significant increment in cpu cycles.
 Verify when value bits increased, no significant increment in cpu cycles.
 Compare with cuckoo hash performance result, lookup cycles should be less.
 
-Test Case: Load balancer performance based on EFD
--------------------------------------------------
+Performance test cases
+==============================
 In EFD sample, EFD work as a flow-level load balancer. Flows are received at
 a front end server before being forwarded to the target back end server for
 processing. This case will measure the performance of flow distribution with
 different parameters.
 
-Value bits: number of bits of value that be stored in EFD table
 Nodes: number of back end nodes
 Entries: number of flows to be added in EFD table
+Value bits: number of bits of value that be stored in EFD table
 
-+--------------+-------+-----------+------------+
-| Value Bits   | Nodes | Entries   | Throughput |
-+--------------+-------+-----------+------------+
-|  8           |   2   |    2M     |            |
-+--------------+-------+-----------+------------+
-|  16          |   2   |    2M     |            |
-+--------------+-------+-----------+------------+
-|  24          |   2   |    2M     |            |
-+--------------+-------+-----------+------------+
-|  32          |   2   |    2M     |            |
-+--------------+-------+-----------+------------+
+Test Case: Load balancer performance based on node numbers
+----------------------------------------------------------------------
+This case will measure the performance based on node numbers.
 
 +--------------+-------+-----------+------------+
 | Value Bits   | Nodes | Entries   | Throughput |
@@ -120,6 +115,10 @@ Entries: number of flows to be added in EFD table
 |  8           |   8   |    2M     |            |
 +--------------+-------+-----------+------------+
 
+Test Case: Load balancer performance based on flow numbers
+-----------------------------------------------------------------------
+This case will measure the performance based on flow numbers.
+
 +--------------+-------+-----------+------------+
 | Value Bits   | Nodes | Entries   | Throughput |
 +--------------+-------+-----------+------------+
@@ -135,3 +134,19 @@ Entries: number of flows to be added in EFD table
 +--------------+-------+-----------+------------+
 |  8           |   2   |    32M    |            |
 +--------------+-------+-----------+------------+
+
+Test Case: Load balancer performance based on value bits
+-----------------------------------------------------------------------
+This case will measure the performance based on value bits.
+
++--------------+-------+-----------+------------+
+| Value Bits   | Nodes | Entries   | Throughput |
++--------------+-------+-----------+------------+
+|  8           |   2   |    2M     |            |
++--------------+-------+-----------+------------+
+|  16          |   2   |    2M     |            |
++--------------+-------+-----------+------------+
+|  24          |   2   |    2M     |            |
++--------------+-------+-----------+------------+
+|  32          |   2   |    2M     |            |
++--------------+-------+-----------+------------+
-- 
1.8.3.1