From: Wenjie Li <wenjiex.a.li@intel.com>
To: dts@dpdk.org
Cc: "Wenjie Li" <wenjiex.a.li@intel.com>
Subject: [dts] [PATCH V1] test_plans: fix build warning
Date: Wed, 22 May 2019 18:51:10 +0800 [thread overview]
Message-ID: <1558522270-63690-1-git-send-email-wenjiex.a.li@intel.com> (raw)
From: "Wenjie Li" <wenjiex.a.li@intel.com>
fix build warning of test plans
Signed-off-by: Wenjie Li <wenjiex.a.li@intel.com>
---
test_plans/dpdk_gro_lib_test_plan.rst | 36 +++++++++++++------
test_plans/dpdk_gso_lib_test_plan.rst | 16 ++++++---
test_plans/macsec_for_ixgbe_test_plan.rst | 14 ++++----
test_plans/vf_l3fwd_test_plan.rst | 4 +--
.../vhost_dequeue_zero_copy_test_plan.rst | 4 ++-
5 files changed, 50 insertions(+), 24 deletions(-)
diff --git a/test_plans/dpdk_gro_lib_test_plan.rst b/test_plans/dpdk_gro_lib_test_plan.rst
index 4ca78ef..410ae68 100644
--- a/test_plans/dpdk_gro_lib_test_plan.rst
+++ b/test_plans/dpdk_gro_lib_test_plan.rst
@@ -87,7 +87,9 @@ Modify the testpmd code as following::
Test flow
=========
-NIC2(In kernel) -> NIC1(DPDK) -> testpmd(csum fwd) -> Vhost -> Virtio-net
+::
+
+ NIC2(In kernel) -> NIC1(DPDK) -> testpmd(csum fwd) -> Vhost -> Virtio-net
Test Case1: DPDK GRO lightmode test with tcp/ipv4 traffic
=========================================================
@@ -119,7 +121,9 @@ Test Case1: DPDK GRO lightmode test with tcp/ipv4 traffic
testpmd>port start 1
testpmd>start
-3. Set up vm with virto device and using kernel virtio-net driver::
+3. Set up vm with virto device and using kernel virtio-net driver:
+
+ ::
taskset -c 13 \
qemu-system-x86_64 -name us-vhost-vm1 \
@@ -172,7 +176,9 @@ Test Case2: DPDK GRO heavymode test with tcp/ipv4 traffic
testpmd>port start 1
testpmd>start
-3. Set up vm with virto device and using kernel virtio-net driver::
+3. Set up vm with virto device and using kernel virtio-net driver:
+
+ ::
taskset -c 13 \
qemu-system-x86_64 -name us-vhost-vm1 \
@@ -225,7 +231,9 @@ Test Case3: DPDK GRO heavymode_flush4 test with tcp/ipv4 traffic
testpmd>port start 1
testpmd>start
-3. Set up vm with virto device and using kernel virtio-net driver::
+3. Set up vm with virto device and using kernel virtio-net driver:
+
+ ::
taskset -c 13 \
qemu-system-x86_64 -name us-vhost-vm1 \
@@ -253,11 +261,15 @@ Test Case4: DPDK GRO test with vxlan traffic
Vxlan topology
--------------
- VM Host
-50.1.1.2 50.1.1.1
- | |
-1.1.2.3 1.1.2.4
- |------------Testpmd------------|
+
+::
+
+ VM Host
+ 50.1.1.2 50.1.1.1
+ | |
+ 1.1.2.3 1.1.2.4
+ |------------Testpmd------------|
+
1. Connect two nic port directly, put nic2 into another namesapce and create Host VxLAN port::
@@ -296,7 +308,9 @@ Vxlan topology
testpmd>port start 1
testpmd>start
-3. Set up vm with virto device and using kernel virtio-net driver::
+3. Set up vm with virto device and using kernel virtio-net driver:
+
+ ::
taskset -c 13 \
qemu-system-x86_64 -name us-vhost-vm1 \
@@ -321,4 +335,4 @@ Vxlan topology
5. Start iperf test, run iperf server at vm side and iperf client at host side, check throughput in log::
Host side : ip netns exec t2 iperf -c 50.1.1.2 -i 2 -t 60 -f g -m
- VM side: iperf -s -f g
+ VM side: iperf -s -f g
\ No newline at end of file
diff --git a/test_plans/dpdk_gso_lib_test_plan.rst b/test_plans/dpdk_gso_lib_test_plan.rst
index e88cff7..8de5f56 100644
--- a/test_plans/dpdk_gso_lib_test_plan.rst
+++ b/test_plans/dpdk_gso_lib_test_plan.rst
@@ -81,7 +81,9 @@ Modify the testpmd code as following::
Test flow
=========
-NIC2(In kernel) <- NIC1(DPDK) <- testpmd(csum fwd) <- Vhost <- Virtio-net
+::
+
+ NIC2(In kernel) <- NIC1(DPDK) <- testpmd(csum fwd) <- Vhost <- Virtio-net
Test Case1: DPDK GSO test with tcp traffic
==========================================
@@ -109,7 +111,9 @@ Test Case1: DPDK GSO test with tcp traffic
testpmd>port start 0
testpmd>start
-3. Set up vm with virto device and using kernel virtio-net driver::
+3. Set up vm with virto device and using kernel virtio-net driver:
+
+ ::
taskset -c 13 \
qemu-system-x86_64 -name us-vhost-vm1 \
@@ -169,7 +173,9 @@ Test Case3: DPDK GSO test with vxlan traffic
testpmd>port start 0
testpmd>start
-3. Set up vm with virto device and using kernel virtio-net driver::
+3. Set up vm with virto device and using kernel virtio-net driver:
+
+ ::
taskset -c 13 \
qemu-system-x86_64 -name us-vhost-vm1 \
@@ -221,7 +227,9 @@ Test Case4: DPDK GSO test with gre traffic
testpmd>port start 0
testpmd>start
-3. Set up vm with virto device and using kernel virtio-net driver::
+3. Set up vm with virto device and using kernel virtio-net driver:
+
+ ::
taskset -c 13 \
qemu-system-x86_64 -name us-vhost-vm1 \
diff --git a/test_plans/macsec_for_ixgbe_test_plan.rst b/test_plans/macsec_for_ixgbe_test_plan.rst
index 893e7a6..79b7d57 100644
--- a/test_plans/macsec_for_ixgbe_test_plan.rst
+++ b/test_plans/macsec_for_ixgbe_test_plan.rst
@@ -73,12 +73,14 @@ Prerequisites
1. Hardware:
* 1x Niantic NIC (2x 10G)
- port0:
- pci address: 07:00.0
- mac address: 00:00:00:00:00:01
- port1:
- pci address: 07:00.1
- mac address: 00:00:00:00:00:02
+ ::
+
+ port0:
+ pci address: 07:00.0
+ mac address: 00:00:00:00:00:01
+ port1:
+ pci address: 07:00.1
+ mac address: 00:00:00:00:00:02
* 2x IXIA ports (10G)
diff --git a/test_plans/vf_l3fwd_test_plan.rst b/test_plans/vf_l3fwd_test_plan.rst
index 97e3ab7..9260cb0 100644
--- a/test_plans/vf_l3fwd_test_plan.rst
+++ b/test_plans/vf_l3fwd_test_plan.rst
@@ -89,7 +89,7 @@ Setup overview
Set up topology as above based on the NIC used.
Test Case 1: Measure performance with kernel PF & dpdk VF
-========================================================
+=========================================================
1, Bind PF ports to kernel driver, i40e or ixgbe, then create 1 VF from each PF,
take XL710 for example::
@@ -132,7 +132,7 @@ Fill out this table with results.
Test Case 2: Measure performance with dpdk PF & dpdk VF
-======================================================
+=======================================================
1, Bind PF ports to igb_uio driver, then create 1 VF from each PF,
take XL710 for example::
diff --git a/test_plans/vhost_dequeue_zero_copy_test_plan.rst b/test_plans/vhost_dequeue_zero_copy_test_plan.rst
index 3ec5e53..3c74c77 100644
--- a/test_plans/vhost_dequeue_zero_copy_test_plan.rst
+++ b/test_plans/vhost_dequeue_zero_copy_test_plan.rst
@@ -323,7 +323,9 @@ Test topology: NIC2(In kernel) <- NIC1(DPDK) <- testpmd(csum fwd) <- Vhost <- Vi
testpmd>port start 0
testpmd>start
-3. Set up vm with virto device and using kernel virtio-net driver::
+3. Set up vm with virto device and using kernel virtio-net driver:
+
+ ::
taskset -c 13 \
qemu-system-x86_64 -name us-vhost-vm1 \
--
2.17.2
next reply other threads:[~2019-05-22 10:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 10:51 Wenjie Li [this message]
2019-05-29 2:36 ` Tu, Lijuan
-- strict thread matches above, loose matches on Subject: below --
2019-09-26 3:27 [dts] [PATCH V1] test_plans:fix " Wenjie Li
2019-09-23 2:53 Wenjie Li
2019-06-10 1:43 [dts] [PATCH V1] test_plans: fix " Wenjie Li
2019-03-01 6:45 Wenjie Li
2019-03-01 7:57 ` 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=1558522270-63690-1-git-send-email-wenjiex.a.li@intel.com \
--to=wenjiex.a.li@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).