From: Wei Ling <weix.ling@intel.com>
To: dts@dpdk.org
Cc: Wei Ling <weix.ling@intel.com>
Subject: [dts][PATCH V1] test_plans/loopback_virtio_user_server_mode_cbdma_test_plan: fix the device_id write error
Date: Tue, 6 Sep 2022 23:00:18 -0400 [thread overview]
Message-ID: <20220907030018.1128370-1-weix.ling@intel.com> (raw)
1.Modify `pdk-devbind.py -b vfio-pci 0000:00:04.0,0000:00:04.1` to
`pdk-devbind.py -b vfio-pci 0000:00:04.0 0000:00:04.1`.
2.Modify the `device_id=net_virtio_user1` to `device_id=net_virtio_user0`.
Signed-off-by: Wei Ling <weix.ling@intel.com>
---
...oopback_virtio_user_server_mode_cbdma_test_plan.rst | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/test_plans/loopback_virtio_user_server_mode_cbdma_test_plan.rst b/test_plans/loopback_virtio_user_server_mode_cbdma_test_plan.rst
index 83d12db5..7a0a8991 100644
--- a/test_plans/loopback_virtio_user_server_mode_cbdma_test_plan.rst
+++ b/test_plans/loopback_virtio_user_server_mode_cbdma_test_plan.rst
@@ -73,7 +73,7 @@ Common steps
<dpdk dir># ./usertools/dpdk-devbind.py -b vfio-pci <DUT port DMA device id>
For example, bind 2 CBDMA channels:
- <dpdk dir># ./usertools/dpdk-devbind.py -b vfio-pci 0000:00:04.0,0000:00:04.1
+ <dpdk dir># ./usertools/dpdk-devbind.py -b vfio-pci 0000:00:04.0 0000:00:04.1
Test Case 1: Loopback packed ring all path multi-queues payload check with server mode and cbdma enable
-------------------------------------------------------------------------------------------------------
@@ -101,8 +101,8 @@ all path multi-queues with server mode when vhost uses the asynchronous operatio
4. Attach pdump secondary process to primary process by same file-prefix::
<dpdk dir># ./x86_64-native-linuxapp-gcc/app/dpdk-pdump -v --file-prefix=virtio-user0 -- \
- --pdump 'device_id=net_virtio_user1,queue=0,rx-dev=./pdump-virtio-rx-q0.pcap,mbuf-size=8000' \
- --pdump 'device_id=net_virtio_user1,queue=1,rx-dev=./pdump-virtio-rx-q1.pcap,mbuf-size=8000'
+ --pdump 'device_id=net_virtio_user0,queue=0,rx-dev=./pdump-virtio-rx-q0.pcap,mbuf-size=8000' \
+ --pdump 'device_id=net_virtio_user0,queue=1,rx-dev=./pdump-virtio-rx-q1.pcap,mbuf-size=8000'
5. Send large pkts from vhost, check loopback performance can get expected and each queue can receive packets::
@@ -213,8 +213,8 @@ all path multi-queues with server mode when vhost uses the asynchronous operatio
4. Attach pdump secondary process to primary process by same file-prefix::
<dpdk dir># ./x86_64-native-linuxapp-gcc/app/dpdk-pdump -v --file-prefix=virtio-user0 -- \
- --pdump 'device_id=net_virtio_user1,queue=0,rx-dev=./pdump-virtio-rx-q0.pcap,mbuf-size=8000' \
- --pdump 'device_id=net_virtio_user1,queue=1,rx-dev=./pdump-virtio-rx-q1.pcap,mbuf-size=8000'
+ --pdump 'device_id=net_virtio_user0,queue=0,rx-dev=./pdump-virtio-rx-q0.pcap,mbuf-size=8000' \
+ --pdump 'device_id=net_virtio_user0,queue=1,rx-dev=./pdump-virtio-rx-q1.pcap,mbuf-size=8000'
5. Send large pkts from vhost, check loopback performance can get expected and each queue can receive packets::
--
2.25.1
next reply other threads:[~2022-09-07 3:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 3:00 Wei Ling [this message]
2022-10-08 6:34 ` lijuan.tu
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=20220907030018.1128370-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).