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_vhost_async_perf_dsa: fix testplan issue
Date: Mon, 24 Apr 2023 15:38:54 +0800 [thread overview]
Message-ID: <20230424073854.2368543-1-weix.ling@intel.com> (raw)
Fix testplan write wrong issue.
Signed-off-by: Wei Ling <weix.ling@intel.com>
---
test_plans/loopback_vhost_async_perf_dsa_test_plan.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/test_plans/loopback_vhost_async_perf_dsa_test_plan.rst b/test_plans/loopback_vhost_async_perf_dsa_test_plan.rst
index 44d8e549..76ac0ddf 100644
--- a/test_plans/loopback_vhost_async_perf_dsa_test_plan.rst
+++ b/test_plans/loopback_vhost_async_perf_dsa_test_plan.rst
@@ -23,7 +23,7 @@ Common steps
2. Bind 1 dsa device to vfio-pci::
- ./usertools/dpdk-devbind.py -b idxd 0000:6f:01.0
+ ./usertools/dpdk-devbind.py -b vfio-pci 0000:6f:01.0
Test Case 1: loopback vhost async test with split ring inorder mergeable path using IDXD kernel driver
------------------------------------------------------------------------------------------------------
@@ -53,7 +53,7 @@ Test Case 1: loopback vhost async test with split ring inorder mergeable path us
testpmd>show port stats all
-5. Quit virtio-user, rerun step 2-4 with different pac ket length, <frame_size> include [64, 128, 256, 512, 1024, 1518].
+5. Quit virtio-user, rerun step 2-4 with different packet length, <frame_size> include [64, 128, 256, 512, 1024, 1518].
Test Case 2: loopback vhost async test with split ring inorder non-mergeable path using IDXD kernel driver
----------------------------------------------------------------------------------------------------------
--
2.25.1
next reply other threads:[~2023-04-24 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 7:38 Wei Ling [this message]
2023-04-26 6:24 ` He, Xingguang
2023-04-27 7:44 ` 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=20230424073854.2368543-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).