From: yufengmx <yufengx.mo@intel.com>
To: dts@dpdk.org, yinan.wang@intel.com, zhaoyan.chen@intel.com,
lihongx.ma@intel.com
Cc: yufengmx <yufengx.mo@intel.com>
Subject: [dts] [PATCH V1 1/1] test_plans/virtio_user_as_exceptional_path: fix clerical
Date: Fri, 6 Sep 2019 14:58:55 +0800 [thread overview]
Message-ID: <20190906065855.11673-2-yufengx.mo@intel.com> (raw)
In-Reply-To: <20190906065855.11673-1-yufengx.mo@intel.com>
error
Fix clerical error. In fact, two queues are used but not one.
Signed-off-by: yufengmx <yufengx.mo@intel.com>
---
test_plans/virtio_user_as_exceptional_path_test_plan.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/test_plans/virtio_user_as_exceptional_path_test_plan.rst b/test_plans/virtio_user_as_exceptional_path_test_plan.rst
index ef6e4a8..a261e15 100644
--- a/test_plans/virtio_user_as_exceptional_path_test_plan.rst
+++ b/test_plans/virtio_user_as_exceptional_path_test_plan.rst
@@ -153,7 +153,7 @@ Flow: tap0<-->vhost-net<-->virtio_user<-->nic0<-->TG
ufw disable
-2. Bind the physical port to igb_uio, launch testpmd with one queue for virtio_user::
+2. Bind the physical port to igb_uio, launch testpmd with two queues for virtio_user::
./dpdk-devbind.py -b igb_uio xx:xx.x # xx:xx.x is the pci addr of nic0
./testpmd -l 1-2 -n 4 --socket-mem 1024,1024 --file-prefix=test2 --vdev=virtio_user0,mac=00:01:02:03:04:05,path=/dev/vhost-net,queue_size=1024,queues=2 -- -i --rxd=1024 --txd=1024 --txq=2 --rxq=2 --nb-cores=1
--
2.21.0
next prev parent reply other threads:[~2019-09-06 6:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 6:58 [dts] [PATCH V1 0/1] test_plans/virtio_user_as_exceptional_path: fix clerical error yufengmx
2019-09-06 6:58 ` yufengmx [this message]
2019-09-18 10:27 ` [dts] [PATCH V1 1/1] test_plans/virtio_user_as_exceptional_path: fix clerical 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=20190906065855.11673-2-yufengx.mo@intel.com \
--to=yufengx.mo@intel.com \
--cc=dts@dpdk.org \
--cc=lihongx.ma@intel.com \
--cc=yinan.wang@intel.com \
--cc=zhaoyan.chen@intel.com \
/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).