[V1] test_plans/vswitch_sample_cbdma_test_plan: fix wrong DMA parameter

Message ID 20221011031946.357089-1-weix.ling@intel.com (mailing list archive)
State Accepted
Headers
Series [V1] test_plans/vswitch_sample_cbdma_test_plan: fix wrong DMA parameter |

Checks

Context Check Description
ci/Intel-dts-format-test success Testing OK
ci/Intel-dts-pylama-test success Testing OK
ci/Intel-dts-doc-test success Testing OK
ci/Intel-dts-suite-test warning SKIPPED

Commit Message

Ling, WeiX Oct. 11, 2022, 3:19 a.m. UTC
  Fix wrong DMA parameter when launch dpdk-vhost.

Signed-off-by: Wei Ling <weix.ling@intel.com>
---
 test_plans/vswitch_sample_cbdma_test_plan.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
  

Comments

He, Xingguang Oct. 21, 2022, 2:16 a.m. UTC | #1
> -----Original Message-----
> From: Wei Ling <weix.ling@intel.com>
> Sent: Tuesday, October 11, 2022 11:20 AM
> To: dts@dpdk.org
> Cc: Ling, WeiX <weix.ling@intel.com>
> Subject: [dts][PATCH V1] test_plans/vswitch_sample_cbdma_test_plan: fix
> wrong DMA parameter
> 
> Fix wrong DMA parameter when launch dpdk-vhost.
> 
> Signed-off-by: Wei Ling <weix.ling@intel.com>
> ---
Acked-by: Xingguang He<xingguang.he@intel.com>
  
Yuan, DukaiX Oct. 21, 2022, 6:36 a.m. UTC | #2
-----Original Message-----
From: Wei Ling <weix.ling@intel.com> 
Sent: 2022年10月11日 11:20
To: dts@dpdk.org
Cc: Ling, WeiX <weix.ling@intel.com>
Subject: [dts][PATCH V1] test_plans/vswitch_sample_cbdma_test_plan: fix wrong DMA parameter

Fix wrong DMA parameter when launch dpdk-vhost.

Signed-off-by: Wei Ling <weix.ling@intel.com>
---
Tested-by: Dukai Yuan<dukaix.yuan@intel.com>
  
Tu, Lijuan Nov. 18, 2022, 7:55 a.m. UTC | #3
On Mon, 10 Oct 2022 23:19:46 -0400, Wei Ling <weix.ling@intel.com> wrote:
> Fix wrong DMA parameter when launch dpdk-vhost.
> 
> Signed-off-by: Wei Ling <weix.ling@intel.com>


Applied, thanks
  

Patch

diff --git a/test_plans/vswitch_sample_cbdma_test_plan.rst b/test_plans/vswitch_sample_cbdma_test_plan.rst
index c7b95753..6d1b76c9 100644
--- a/test_plans/vswitch_sample_cbdma_test_plan.rst
+++ b/test_plans/vswitch_sample_cbdma_test_plan.rst
@@ -101,7 +101,7 @@  This case tests that the imix packets can forward normally with two VMs in PVP t
 6. Quit and relaunch dpdk-vhost by below command::
 
 	./x86_64-native-linuxapp-gcc/examples/dpdk-vhost -l 26-28 -n 4 -a 0000:af:00.0 -a 0000:00:04.0 -a 0000:00:04.1 -a 0000:00:04.2 -a 0000:00:04.3  -- \
-	-p 0x1 --mergeable 1 --vm2vm 1  --stats 1 --socket-file /root/dpdk/vhost-net0 --socket-file /root/dpdk/vhost-net1 --dmas [txd0@0000:00:01.0,rxd1@0000:00:01.1] --client--total-num-mbufs 600000
+	-p 0x1 --mergeable 1 --vm2vm 1  --stats 1 --socket-file /root/dpdk/vhost-net0 --socket-file /root/dpdk/vhost-net1 --dmas [txd0@0000:00:04.0,rxd1@0000:00:04.1] --client--total-num-mbufs 600000
 
 7. Start packets from two virtio-user side individually to let vswitch know the mac addr::
 
@@ -172,7 +172,7 @@  This case checks that the split ring with CBDMA channel can work stably when the
 2. On host, launch dpdk-vhost by below command::
 
 	./x86_64-native-linuxapp-gcc/examples/dpdk-vhost -l 26-28 -n 4 -a 0000:af:00.0 -a 0000:00:04.0 -a 0000:00:04.1 -a 0000:00:04.2 -a 0000:00:04.3 -- -p 0x1 --mergeable 1 --vm2vm 1  \
-	--socket-file /root/dpdk/vhost-net0 --socket-file /root/dpdk/vhost-net1 --dmas [txd0@0000:00:04.0,rxd0@0000:00:04.1,txd1@0000:00:01.2,rxd1@0000:00:01.3] --client --total-num-mbufs 600000
+	--socket-file /root/dpdk/vhost-net0 --socket-file /root/dpdk/vhost-net1 --dmas [txd0@0000:00:04.0,rxd0@0000:00:04.1,txd1@0000:00:04.2,rxd1@0000:00:04.3] --client --total-num-mbufs 600000
 
 3. Start VM0 with qemu::
 
@@ -245,7 +245,7 @@  This case checks that the split ring with CBDMA channel can work stably when the
 9. Quit and relaunch dpdk-vhost with below command::
 
 	./x86_64-native-linuxapp-gcc/examples/dpdk-vhost -l 26-28 -n 4 -a 0000:af:00.0 -a 0000:00:04.0 -a 0000:00:04.1 -a 0000:00:04.2 -a 0000:00:04.3 -- -p 0x1 --mergeable 1 --vm2vm 1  \
-	--socket-file /root/dpdk/vhost-net0 --socket-file /root/dpdk/vhost-net1 --dmas [txd0@0000:00:04.0,rxd1@0000:00:01.3] --client --total-num-mbufs 600000
+	--socket-file /root/dpdk/vhost-net0 --socket-file /root/dpdk/vhost-net1 --dmas [txd0@0000:00:04.0,rxd1@0000:00:04.3] --client --total-num-mbufs 600000
 
 10. Rerun step 6-7,check vhost can stable work and get expected throughput.