diff --git a/test_plans/cbdma_test_plan.rst b/test_plans/cbdma_test_plan.rst
index 10038754..3ddbd5a2 100644
--- a/test_plans/cbdma_test_plan.rst
+++ b/test_plans/cbdma_test_plan.rst
@@ -1,68 +1,109 @@
 .. SPDX-License-Identifier: BSD-3-Clause
    Copyright(c) 2019 Intel Corporation
 
-===============
+================
 CBDMA test plan
-===============
-
-Sample Application of packet copying using Intel Quick Data Technology
-======================================================================
+================
 
-Overview
---------
+Description
+===========
 
 This sample is intended as a demonstration of the basic components of a DPDK
-forwarding application and example of how to use IOAT driver API to make
-packets copies. Also, this application can be used to compare performance of
-memory copy with different packet size between CPU and DMA engine. The application
-will print out statistics each second. The stats shows received/send packets and
-packets dropped or failed to copy. The application can be launched in various
-configurations depending on provided parameters. Each port can use up to 2 lcores:
-one of lcore receives incoming traffic and makes a copy of each packet, the second
-lcore then updates MAC address and sends the copy. If one lcore per port is used,
-both operations are done sequentially. For each configuration an additional lcore
-is needed since master lcore in use which is responsible for configuration,
-statistics printing and safe deinitialization of all ports and devices. Also, the
-application can use 8 ports in maximum.
-
-Running the Application
------------------------
+forwarding application and example of how to use the DMAdev API to make a packet
+copy application.
+
+Also while forwarding, the MAC addresses are affected as follows:
+
+*   The source MAC address is replaced by the TX port MAC address
+
+*   The destination MAC address is replaced by  02:00:00:00:00:TX_PORT_ID
+
+This application can be used to compare performance of using software packet
+copy with copy done using a DMA device for different sizes of packets.
+The example will print out statistics each second. The stats shows
+received/send packets and packets dropped or failed to copy.
 
 In order to run the hardware copy application, the copying device
 needs to be bound to user-space IO driver.
 
-Refer to the *IOAT Rawdev Driver for Intel QuickData Technology*
-guide for information on using the driver.
+Refer to the "DMAdev library" chapter in the "Programmers guide" for information
+on using the library.
 
 The application requires a number of command line options:
 
 .. code-block:: console
 
-    x86_64-native-linuxapp-gcc/examples/dpdk-dma [EAL options] -- -p MASK [-q NQ] [-s RS] [-c <sw|hw>]
-        [--[no-]mac-updating]
+    ./<build_dir>/examples/dpdk-dma [EAL options] -- [-p MASK] [-q NQ] [-s RS] [-c <sw|hw>]
+        [--[no-]mac-updating] [-b BS] [-f FS] [-i SI]
 
 where,
 
-*   p MASK: A hexadecimal bitmask of the ports to configure
+*   p MASK: A hexadecimal bitmask of the ports to configure (default is all)
 
-*   q NQ: Number of Rx queues used per port equivalent to CBDMA channels
-    per port
+*   q NQ: Number of Rx queues used per port equivalent to DMA channels
+    per port (default is 1)
 
 *   c CT: Performed packet copy type: software (sw) or hardware using
-    DMA (hw)
+    DMA (hw) (default is hw)
 
-*   s RS: Size of IOAT rawdev ring for hardware copy mode or rte_ring for
-    software copy mode
+*   s RS: Size of dmadev descriptor ring for hardware copy mode or rte_ring for
+    software copy mode (default is 2048)
 
 *   --[no-]mac-updating: Whether MAC address of packets should be changed
-    or not
+    or not (default is mac-updating)
 
-Packet pipeline: 
-================
+*   b BS: set the DMA batch size
+
+*   f FS: set the max frame size
+
+*   i SI: set the interval, in second, between statistics prints (default is 1)
+
+The application can be launched in various configurations depending on
+provided parameters. The app can use up to 2 lcores: one of them receives
+incoming traffic and makes a copy of each packet. The second lcore then
+updates MAC address and sends the copy. If one lcore per port is used,
+both operations are done sequentially. For each configuration an additional
+lcore is needed since the main lcore does not handle traffic but is
+responsible for configuration, statistics printing and safe shutdown of
+all ports and devices.
+
+The application can use a maximum of 8 ports.
+
+To run the application in a Linux environment with 3 lcores (the main lcore,
+plus two forwarding cores), a single port (port 0), software copying and MAC
+updating issue the command:
+
+    $ ./<build_dir>/examples/dpdk-dma -l 0-2 -n 2 -- -p 0x1 --mac-updating -c sw
+
+To run the application in a Linux environment with 2 lcores (the main lcore,
+plus one forwarding core), 2 ports (ports 0 and 1), hardware copying and no MAC
+updating issue the command:
+
+    $ ./<build_dir>/examples/dpdk-dma -l 0-1 -n 1 -- -p 0x3 --no-mac-updating -c hw
+
+Prerequisites
+=============
+
+Test flow
+---------
+    
 NIC RX -> copy packet -> free original -> update mac addresses -> NIC TX
 
-Test Case1: CBDMA basic test with differnet size packets
-========================================================
+General set up
+--------------
+1. Compile DPDK::
+
+    # CC=gcc meson --werror -Denable_kmods=True -Dlibdir=lib -Dexamples=all --default-library=static <dpdk build dir>
+    # ninja -C <dpdk build dir> -j 110
+    For example:
+    CC=gcc meson --werror -Denable_kmods=True -Dlibdir=lib -Dexamples=all --default-library=static x86_64-native-linuxapp-gcc
+    ninja -C x86_64-native-linuxapp-gcc -j 110
+
+Test case
+=========
+
+Test Case 1: CBDMA basic test with differnet size packets
+----------------------------------------------------------
 
 1.Bind one cbdma port and one nic port to vfio-pci driver.
 
@@ -74,8 +115,8 @@ Test Case1: CBDMA basic test with differnet size packets
 
 4.Check performance from “Total packets Tx” and check log includes "Worker Threads = 1, Copy Mode = hw".
 
-Test Case2: CBDMA test with multi-threads
-=========================================
+Test Case 2: CBDMA test with multi-threads
+-------------------------------------------
 
 1.Bind one cbdma port and one nic port to vfio-pci driver.
 
@@ -87,8 +128,8 @@ Test Case2: CBDMA test with multi-threads
 
 4.Check performance from “Total packets Tx” and check log includes "Worker Threads = 2, Copy Mode = hw".
 
-Test Case3: CBDMA test with multi nic ports
-===========================================
+Test Case 3: CBDMA test with multi nic ports
+---------------------------------------------
 
 1.Bind two cbdma ports and two nic ports to vfio-pci driver.
 
@@ -100,8 +141,8 @@ Test Case3: CBDMA test with multi nic ports
 
 4.Check stats of two ports, each port's performance shows in “Total packets Tx” and each port's log includes "Worker Threads = 2, Copy Mode = hw".
 
-Test Case4: CBDMA test with multi-queues
-========================================
+Test Case 4: CBDMA test with multi-queues
+------------------------------------------
 
 1.Bind two cbdma ports and one nic port to vfio-pci driver.
 
@@ -111,13 +152,13 @@ Test Case4: CBDMA test with multi-queues
 
 3. Send random ip packets (64B, 256B, 512B, 1024B, IMIX) from TG to NIC port.
 
-4. Check stats of ioat app, "Worker Threads = 2, Copy Mode = hw, Rx Queues = 2" and each ioat channel can enqueue packets.
+4. Check stats of dma app, "Worker Threads = 2, Copy Mode = hw, Rx Queues = 2" and each dma channel can enqueue packets.
 
 5. Repeat step1 to step4 with queue number 4 and qemu number 8, also bind same number cbdma ports.
 Check performance gains status when queue numbers added.
 
-Test Case5: CBDMA performance cmparison between mac-updating and no-mac-updating
-================================================================================
+Test Case 5: CBDMA performance cmparison between mac-updating and no-mac-updating
+----------------------------------------------------------------------------------
 
 1.Bind one cbdma ports and one nic port to vfio-pci driver.
 
@@ -127,7 +168,7 @@ Test Case5: CBDMA performance cmparison between mac-updating and no-mac-updating
 
 3. Send random ip 64B packets from TG.
 
-4. Check performance from ioat app::
+4. Check performance from dma app::
 
     Total packets Tx:                   xxx [pps]
 
@@ -137,12 +178,12 @@ Test Case5: CBDMA performance cmparison between mac-updating and no-mac-updating
 
 6. Send random ip 64B packets from TG.
 
-7. Check performance from ioat app::
+7. Check performance from dma app::
 
     Total packets Tx:                   xxx [pps]
   
-Test Case6: CBDMA performance cmparison between HW copies and SW copies using different packet size
-===================================================================================================
+Test Case 6: CBDMA performance cmparison between HW copies and SW copies using different packet size
+-----------------------------------------------------------------------------------------------------
 
 1.Bind four cbdma pors and one nic port to vfio-pci driver.
 
@@ -152,7 +193,7 @@ Test Case6: CBDMA performance cmparison between HW copies and SW copies using di
 
 3. Send random ip packets from TG.
 
-4. Check performance from ioat app::
+4. Check performance from dma app::
 
     Total packets Tx:                   xxx [pps]
 
@@ -162,12 +203,12 @@ Test Case6: CBDMA performance cmparison between HW copies and SW copies using di
 
 6. Send random ip packets from TG.
 
-7. Check performance from ioat app and compare with hw copy test::
+7. Check performance from dma app and compare with hw copy test::
 
     Total packets Tx:                   xxx [pps]
 
-Test Case7: CBDMA multi application mode test
-=============================================
+Test Case 7: CBDMA multi application mode test
+-----------------------------------------------
 
 1.Bind four cbdma ports to vfio-pci driver.
 
