From: Wei Ling <weix.ling@intel.com>
To: dts@dpdk.org
Cc: Wei Ling <weix.ling@intel.com>
Subject: [dts][PATCH V1] test_plans/*_dsa_test_plan.rst: fix create DSA work queue miss parameter issue
Date: Wed, 12 Oct 2022 01:43:30 -0400 [thread overview]
Message-ID: <20221012054330.607704-1-weix.ling@intel.com> (raw)
Fix create DSA work queue miss 1 <numDevices> parameter issue
in all DSA related test plans.
Signed-off-by: Wei Ling <weix.ling@intel.com>
---
test_plans/basic_4k_pages_dsa_test_plan.rst | 2 +-
test_plans/loopback_virtio_user_server_mode_dsa_test_plan.rst | 2 +-
test_plans/pvp_vhost_dsa_test_plan.rst | 2 +-
test_plans/vm2vm_virtio_net_perf_dsa_test_plan.rst | 2 +-
test_plans/vm2vm_virtio_user_dsa_test_plan.rst | 2 +-
test_plans/vswitch_sample_dsa_test_plan.rst | 2 +-
6 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/test_plans/basic_4k_pages_dsa_test_plan.rst b/test_plans/basic_4k_pages_dsa_test_plan.rst
index 69cf7fc1..666704ae 100644
--- a/test_plans/basic_4k_pages_dsa_test_plan.rst
+++ b/test_plans/basic_4k_pages_dsa_test_plan.rst
@@ -94,7 +94,7 @@ Common steps
3. Bind DSA devices to kernel idxd driver, and configure Work Queue (WQ)::
<dpdk dir># ./usertools/dpdk-devbind.py -b idxd <numDevices * 2>
- <dpdk dir># ./drivers/dma/dma/idxd/dpdk_idxd_cfg.py -q <numWq>
+ <dpdk dir># ./drivers/dma/dma/idxd/dpdk_idxd_cfg.py -q <numWq> <numDevices>
.. note::
diff --git a/test_plans/loopback_virtio_user_server_mode_dsa_test_plan.rst b/test_plans/loopback_virtio_user_server_mode_dsa_test_plan.rst
index a96ce539..55c71c99 100644
--- a/test_plans/loopback_virtio_user_server_mode_dsa_test_plan.rst
+++ b/test_plans/loopback_virtio_user_server_mode_dsa_test_plan.rst
@@ -88,7 +88,7 @@ Common steps
2. Bind DSA devices to kernel idxd driver, and configure Work Queue (WQ)::
<dpdk dir># ./usertools/dpdk-devbind.py -b idxd <numDevices>
- <dpdk dir># ./drivers/dma/idxd/dpdk_idxd_cfg.py -q <numWq>
+ <dpdk dir># ./drivers/dma/idxd/dpdk_idxd_cfg.py -q <numWq> <numDevices>
.. note::
diff --git a/test_plans/pvp_vhost_dsa_test_plan.rst b/test_plans/pvp_vhost_dsa_test_plan.rst
index 74205b79..9972ad0c 100644
--- a/test_plans/pvp_vhost_dsa_test_plan.rst
+++ b/test_plans/pvp_vhost_dsa_test_plan.rst
@@ -104,7 +104,7 @@ Common steps
3. Bind DSA devices to kernel idxd driver, and configure Work Queue (WQ)::
<dpdk dir># ./usertools/dpdk-devbind.py -b idxd <numDevices>
- <dpdk dir># ./drivers/dma/idxd/dpdk_idxd_cfg.py -q <numWq>
+ <dpdk dir># ./drivers/dma/idxd/dpdk_idxd_cfg.py -q <numWq> <numDevices>
.. note::
diff --git a/test_plans/vm2vm_virtio_net_perf_dsa_test_plan.rst b/test_plans/vm2vm_virtio_net_perf_dsa_test_plan.rst
index 70bb371a..6372240b 100644
--- a/test_plans/vm2vm_virtio_net_perf_dsa_test_plan.rst
+++ b/test_plans/vm2vm_virtio_net_perf_dsa_test_plan.rst
@@ -95,7 +95,7 @@ Common steps
2. Bind DSA devices to kernel idxd driver, and configure Work Queue (WQ)::
<dpdk dir># ./usertools/dpdk-devbind.py -b idxd <numDevices * 2>
- <dpdk dir># ./drivers/dma/idxd/dpdk_idxd_cfg.py -q <numWq>
+ <dpdk dir># ./drivers/dma/idxd/dpdk_idxd_cfg.py -q <numWq> <numDevices>
.. note::
diff --git a/test_plans/vm2vm_virtio_user_dsa_test_plan.rst b/test_plans/vm2vm_virtio_user_dsa_test_plan.rst
index 8f2f7133..369fe076 100644
--- a/test_plans/vm2vm_virtio_user_dsa_test_plan.rst
+++ b/test_plans/vm2vm_virtio_user_dsa_test_plan.rst
@@ -86,7 +86,7 @@ Common steps
2. Bind DSA devices to kernel idxd driver, and configure Work Queue (WQ)::
<dpdk dir># ./usertools/dpdk-devbind.py -b idxd <numDevices * 2>
- <dpdk dir># ./drivers/dma/idxd/dpdk_idxd_cfg.py -q <numWq>
+ <dpdk dir># ./drivers/dma/idxd/dpdk_idxd_cfg.py -q <numWq> <numDevices>
.. note::
diff --git a/test_plans/vswitch_sample_dsa_test_plan.rst b/test_plans/vswitch_sample_dsa_test_plan.rst
index e9d74d33..1641e051 100644
--- a/test_plans/vswitch_sample_dsa_test_plan.rst
+++ b/test_plans/vswitch_sample_dsa_test_plan.rst
@@ -80,7 +80,7 @@ Common steps
3. Bind DSA devices to kernel idxd driver, and configure Work Queue (WQ)::
<dpdk dir># ./usertools/dpdk-devbind.py -b idxd <numDevices * 2>
- <dpdk dir># ./<dpdk build dir>drivers/dma/idxd/dpdk_idxd_cfg.py -q <numWq>
+ <dpdk dir># ./<dpdk build dir>drivers/dma/idxd/dpdk_idxd_cfg.py -q <numWq> <numDevices>
.. note::
--
2.25.1
next reply other threads:[~2022-10-12 5:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 5:43 Wei Ling [this message]
2022-10-21 2:18 ` He, Xingguang
2022-10-21 6:35 ` Yuan, DukaiX
2022-11-18 7:54 ` 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=20221012054330.607704-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).