diff mbox series

[V1,1/2] test_plans/vhost_virtio_user_interrupt_test_plan: delete -P parameter when start l3fwd-power

Message ID 20220527034802.530260-1-weix.ling@intel.com (mailing list archive)
State Superseded
Headers
Series delete -P parameter when start l3fwd-power |

Commit Message

Ling, WeiX May 27, 2022, 3:48 a.m. UTC 
  If start dpdk-l3fwd-power with -P parameter, it will start failed,
so delete -P parameter.

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

Comments

Tu, Lijuan May 28, 2022, 8:49 a.m. UTC | #1 
> -----Original Message-----
> From: Wei Ling <weix.ling@intel.com>
> Sent: 2022年5月27日 11:48
> To: dts@dpdk.org
> Cc: Ling, WeiX <weix.ling@intel.com>
> Subject: [dts][PATCH V1 1/2] test_plans/vhost_virtio_user_interrupt_test_plan: delete -P parameter when
> start l3fwd-power
> 
> If start dpdk-l3fwd-power with -P parameter, it will start failed, so delete -P parameter.
> 
> Signed-off-by: Wei Ling <weix.ling@intel.com>

It seems a bug of dpdk, if not, please add the reason. 
Thanks.
diff mbox series

Patch

diff --git a/test_plans/vhost_virtio_user_interrupt_test_plan.rst b/test_plans/vhost_virtio_user_interrupt_test_plan.rst
index 1b86ca2b..9a7257a5 100644
--- a/test_plans/vhost_virtio_user_interrupt_test_plan.rst
+++ b/test_plans/vhost_virtio_user_interrupt_test_plan.rst
@@ -23,7 +23,7 @@  flow: TG --> NIC --> Vhost --> Virtio
 2. Start l3fwd-power with a virtio-user device::
 
     ./x86_64-native-linuxapp-gcc/examples/dpdk-l3fwd-power -c 0xc000 -n 4 --log-level='user1,7' --no-pci --file-prefix=l3fwd-pwd \
-    --vdev=virtio_user0,path=./vhost-net -- -p 1 -P --config="(0,0,14)" --parse-ptype
+    --vdev=virtio_user0,path=./vhost-net -- -p 1 --config="(0,0,14)" --parse-ptype
 
 3. Send packets with packet generator, check the virtio-user related core can be wakeup status.
 
@@ -39,7 +39,7 @@  flow: Tap --> Vhost-net --> Virtio
 1. Start l3fwd-power with a virtio-user device, vhost-net as backend::
 
     ./x86_64-native-linuxapp-gcc/examples/dpdk-l3fwd-power -c 0xc000 -n 4 --log-level='user1,7' --no-pci --file-prefix=l3fwd-pwd \
-    --vdev=virtio_user0,path=/dev/vhost-net -- -p 1 -P --config="(0,0,14)" --parse-ptype
+    --vdev=virtio_user0,path=/dev/vhost-net -- -p 1 --config="(0,0,14)" --parse-ptype
 
 2. Vhost-net will generate one tap device, normally, it's TAP0, config it and generate packets on it using pind cmd::
 
@@ -93,7 +93,7 @@  flow: TG --> NIC --> Vhost --> Virtio
 2. Start l3fwd-power with a virtio-user device::
 
     ./x86_64-native-linuxapp-gcc/examples/dpdk-l3fwd-power -c 0xc000 -n 4 --log-level='user1,7' --no-pci --file-prefix=l3fwd-pwd \
-    --vdev=virtio_user0,path=./vhost-net,packed_vq=1 -- -p 1 -P --config="(0,0,14)" --parse-ptype
+    --vdev=virtio_user0,path=./vhost-net,packed_vq=1 -- -p 1 --config="(0,0,14)" --parse-ptype
 
 3. Send packets with packet generator, check the virtio-user related core can be wakeup status.
 
@@ -109,7 +109,7 @@  flow: Tap --> Vhost-net --> Virtio
 1. Start l3fwd-power with a virtio-user device, vhost-net as backend::
 
     ./x86_64-native-linuxapp-gcc/examples/dpdk-l3fwd-power -c 0xc000 -n 4 --log-level='user1,7' --no-pci --file-prefix=l3fwd-pwd \
-    --vdev=virtio_user0,path=/dev/vhost-net,packed_vq=1 -- -p 1 -P --config="(0,0,14)" --parse-ptype
+    --vdev=virtio_user0,path=/dev/vhost-net,packed_vq=1 -- -p 1 --config="(0,0,14)" --parse-ptype
 
 2. Vhost-net will generate one tap device, normally, it's TAP0, config it and generate packets on it using pind cmd::