test suite reviews and discussions
 help / color / mirror / Atom feed
From: Wei Ling <weix.ling@intel.com>
To: dts@dpdk.org
Cc: Wei Ling <weix.ling@intel.com>
Subject: [dts][PATCH V1 1/2] test_plans/dma_test_plan: rename testplan
Date: Mon, 12 Dec 2022 14:06:50 +0800	[thread overview]
Message-ID: <20221212060650.2779428-1-weix.ling@intel.com> (raw)

Rename test_plans/cbdma_test_plan.rst to dma_test_plan.rst.

Signed-off-by: Wei Ling <weix.ling@intel.com>
---
 ...{cbdma_test_plan.rst => dma_test_plan.rst} | 46 +++++++++----------
 1 file changed, 23 insertions(+), 23 deletions(-)
 rename test_plans/{cbdma_test_plan.rst => dma_test_plan.rst} (86%)

diff --git a/test_plans/cbdma_test_plan.rst b/test_plans/dma_test_plan.rst
similarity index 86%
rename from test_plans/cbdma_test_plan.rst
rename to test_plans/dma_test_plan.rst
index 3ddbd5a2..c4dfeaf1 100644
--- a/test_plans/cbdma_test_plan.rst
+++ b/test_plans/dma_test_plan.rst
@@ -105,9 +105,9 @@ 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.
+1.Bind 1 CBDMA port and 1 NIC port to vfio-pci driver.
 
-2.Launch dma app::
+2.Launch DMA APP::
 
 ./x86_64-native-linuxapp-gcc/examples/dpdk-dma -l 0-1 -n 2 -- -p 0x1 --mac-updating -c hw
 
@@ -118,9 +118,9 @@ Test Case 1: CBDMA basic test with differnet size packets
 Test Case 2: CBDMA test with multi-threads
 -------------------------------------------
 
-1.Bind one cbdma port and one nic port to vfio-pci driver.
+1.Bind 1 CBDMA port and 1 NIC port to vfio-pci driver.
 
-2.Launch dma app with three cores::
+2.Launch DMA APP with 3 cores::
 
 ./x86_64-native-linuxapp-gcc/examples/dpdk-dma -l 0-2 -n 2 -- -p 0x1 --mac-updating -c hw
 
@@ -128,12 +128,12 @@ Test Case 2: CBDMA test with multi-threads
 
 4.Check performance from “Total packets Tx” and check log includes "Worker Threads = 2, Copy Mode = hw".
 
-Test Case 3: 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.
+1.Bind 2 CBDMA ports and 2 NIC ports to vfio-pci driver.
 
-2.Launch dma app with multi-ports::
+2.Launch DMA APP with multi-ports::
 
 ./x86_64-native-linuxapp-gcc/examples/dpdk-dma -l 0-4 -n 2 -- -p 0x3 -q 1 --mac-updating -c hw
 
@@ -144,79 +144,79 @@ Test Case 3: CBDMA test with multi nic ports
 Test Case 4: CBDMA test with multi-queues
 ------------------------------------------
 
-1.Bind two cbdma ports and one nic port to vfio-pci driver.
+1.Bind 2 CBDMA ports and 1 NIC port to vfio-pci driver.
 
-2.Launch dma app with multi-queues::
+2.Launch DMA APP with multi-queues::
 
 ./x86_64-native-linuxapp-gcc/examples/dpdk-dma -l 0-2 -n 2 -- -p 0x1 -q 2 --mac-updating -c hw
 
 3. Send random ip packets (64B, 256B, 512B, 1024B, IMIX) from TG to NIC port.
 
-4. Check stats of dma app, "Worker Threads = 2, Copy Mode = hw, Rx Queues = 2" and each dma 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.
+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 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.
+1.Bind 1 CBDMA ports and 1 NIC port to vfio-pci driver.
 
-2.Launch dma app::
+2.Launch DMA APP::
 
 ./x86_64-native-linuxapp-gcc/examples/dpdk-dma -l 0-1 -n 2 -- -p 0x1 -q 2 --no-mac-updating -c hw
 
 3. Send random ip 64B packets from TG.
 
-4. Check performance from dma app::
+4. Check performance from DMA APP::
 
     Total packets Tx:                   xxx [pps]
 
-5.Launch dma app::
+5.Launch DMA APP::
 
 ./x86_64-native-linuxapp-gcc/examples/dpdk-dma -l 0-1 -n 2 -- -p 0x1 -q 2 --mac-updating -c hw
 
 6. Send random ip 64B packets from TG.
 
-7. Check performance from dma app::
+7. Check performance from DMA APP::
 
     Total packets Tx:                   xxx [pps]
   
 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.
+1.Bind 4 cbdma pors and 1 NIC port to vfio-pci driver.
 
-2.Launch dma app with three cores::
+2.Launch DMA APP with 3 cores::
 
 ./x86_64-native-linuxapp-gcc/examples/dpdk-dma -l 0-2 -n 2 -- -p 0x1 -q 4 --mac-updating  -c hw
 
 3. Send random ip packets from TG.
 
-4. Check performance from dma app::
+4. Check performance from DMA APP::
 
     Total packets Tx:                   xxx [pps]
 
-5.Launch dma app with three cores::
+5.Launch DMA APP with three cores::
 
 ./x86_64-native-linuxapp-gcc/examples/dpdk-dma -l 0-2 -n 2 -- -p 0x1 -q 4 --mac-updating -c sw
 
 6. Send random ip packets from TG.
 
-7. Check performance from dma 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 Case 7: CBDMA multi application mode test
 -----------------------------------------------
 
-1.Bind four cbdma ports to vfio-pci driver.
+1.Bind 4 CBDMA ports to vfio-pci driver.
 
 2.Launch test-pmd app with three cores and proc_type primary:
 
  ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 0-2 -n 2 -- -p 0x1 -q 4  --proc-type=primary
 
-3. Launch another dma app with three cores and proc_type secondary:
+3. Launch another DMA APP with three cores and proc_type secondary:
 
 ./x86_64-native-linuxapp-gcc/examples/dpdk-dma -l 0-2 -n 2 -- -p 0x1 -q 4  --proc-type=secondary
 
-- 
2.25.1


                 reply	other threads:[~2022-12-12  6:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221212060650.2779428-1-weix.ling@intel.com \
    --to=weix.ling@intel.com \
    --cc=dts@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).