From: Wei Ling <weix.ling@intel.com>
To: dts@dpdk.org
Cc: Wei Ling <weix.ling@intel.com>
Subject: [dts][PATCH V1] test_plans/vhost_event_idx_interrupt_test_plan: fix lcore index error
Date: Thu, 22 Dec 2022 11:10:09 +0800 [thread overview]
Message-ID: <20221222031009.175142-1-weix.ling@intel.com> (raw)
Fix lcore index error in testcase2&3.
Signed-off-by: Wei Ling <weix.ling@intel.com>
---
test_plans/vhost_event_idx_interrupt_test_plan.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/test_plans/vhost_event_idx_interrupt_test_plan.rst b/test_plans/vhost_event_idx_interrupt_test_plan.rst
index cca91dae..18e66efb 100644
--- a/test_plans/vhost_event_idx_interrupt_test_plan.rst
+++ b/test_plans/vhost_event_idx_interrupt_test_plan.rst
@@ -126,10 +126,10 @@ Test Case 2: wake up split ring vhost-user cores with event idx interrupt mode 1
6. Check vhost related cores are waked up with l3fwd-power log, such as following::
- L3FWD_POWER: lcore 0 is waked up from rx interrupt on port 0 queue 0
+ L3FWD_POWER: lcore 1 is waked up from rx interrupt on port 0 queue 0
...
...
- L3FWD_POWER: lcore 15 is waked up from rx interrupt on port 0 queue 15
+ L3FWD_POWER: lcore 16 is waked up from rx interrupt on port 0 queue 15
Test Case 3: wake up split ring vhost-user cores by multi virtio-net in VMs with event idx interrupt mode
=========================================================================================================
@@ -299,10 +299,10 @@ Test Case 5: wake up packed ring vhost-user cores with event idx interrupt mode
6. Check vhost related cores are waked up with l3fwd-power log, such as following::
- L3FWD_POWER: lcore 0 is waked up from rx interrupt on port 0 queue 0
+ L3FWD_POWER: lcore 1 is waked up from rx interrupt on port 0 queue 0
...
...
- L3FWD_POWER: lcore 15 is waked up from rx interrupt on port 0 queue 15
+ L3FWD_POWER: lcore 16 is waked up from rx interrupt on port 0 queue 15
Test Case 6: wake up packed ring vhost-user cores by multi virtio-net in VMs with event idx interrupt mode
==========================================================================================================
--
2.25.1
next reply other threads:[~2022-12-22 3:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 3:10 Wei Ling [this message]
2022-12-22 9:39 ` He, Xingguang
2022-12-26 4:48 ` 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=20221222031009.175142-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).