From: Yinan Wang <yinan.wang@intel.com>
To: dts@dpdk.org
Cc: Yinan Wang <yinan.wang@intel.com>
Subject: [dts] [PATCH v1] test_plans/virtio_event_idx_interrupt_test_plan.rst
Date: Wed, 23 Sep 2020 12:48:19 -0400 [thread overview]
Message-ID: <20200923164819.1266224-1-yinan.wang@intel.com> (raw)
Update typo issue.
Signed-off-by: Yinan Wang <yinan.wang@intel.com>
---
test_plans/virtio_event_idx_interrupt_test_plan.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/test_plans/virtio_event_idx_interrupt_test_plan.rst b/test_plans/virtio_event_idx_interrupt_test_plan.rst
index eb26a13..af527f6 100644
--- a/test_plans/virtio_event_idx_interrupt_test_plan.rst
+++ b/test_plans/virtio_event_idx_interrupt_test_plan.rst
@@ -299,7 +299,7 @@ Test Case 7: Split ring virtio-pci driver reload test with CBDMA enabled
Test Case 8: Wake up split ring virtio-net cores with event idx interrupt mode and cbdma enabled 16 queues test
================================================================================================================
-1. Bind one nic port to igb_uio, then launch the vhost sample by below commands::
+1. Bind one nic port and 16 cbdma channels to igb_uio, then launch the vhost sample by below commands::
rm -rf vhost-net*
./testpmd -l 1-17 -n 4 --file-prefix=vhost --vdev 'net_vhost,iface=vhost-net,queues=16,client=1,dmas=[txq0@80:04.0;txq1@80:04.1;txq2@80:04.2;txq3@80:04.3;txq4@80:04.4;txq5@80:04.5;txq6@80:04.6;txq7@80:04.7;txq8@00:04.0;txq9@00:04.1;txq10@00:04.2;txq11@00:04.3;txq12@00:04.4;txq13@00:04.5;txq14@00:04.6;txq15@00:04.7],dmathr=64' -- -i --nb-cores=16 --txd=1024 --rxd=1024 --rxq=16 --txq=16
--
2.25.1
next reply other threads:[~2020-09-23 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 16:48 Yinan Wang [this message]
2020-10-12 7:42 ` Tu, Lijuan
-- strict thread matches above, loose matches on Subject: below --
2020-09-22 16:27 Yinan Wang
2020-10-12 7:45 ` Tu, Lijuan
2020-08-21 10:31 Yinan Wang
2020-08-27 2:02 ` 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=20200923164819.1266224-1-yinan.wang@intel.com \
--to=yinan.wang@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).