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/vhost_virtio_user_interrupt_test_plan: delete -P parameter when start l3fwd-power
Date: Thu, 26 May 2022 23:48:02 -0400 [thread overview]
Message-ID: <20220527034802.530260-1-weix.ling@intel.com> (raw)
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(-)
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::
--
2.25.1
next reply other threads:[~2022-05-27 3:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 3:48 Wei Ling [this message]
2022-05-28 8:49 ` Tu, Lijuan
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=20220527034802.530260-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).