test suite reviews and discussions
 help / color / mirror / Atom feed
From: Yinan Wang <yinan.wang@intel.com>
To: dts@dpdk.org
Cc: Yinan Wang <yinan.wang@intel.com>
Subject: [dts]  [PATCH v1] test_plans/dpdk_gro_lib_test_plan.rst
Date: Thu, 20 Aug 2020 06:12:46 -0400	[thread overview]
Message-ID: <20200820101246.15902-1-yinan.wang@intel.com> (raw)

Add vhost code change before test

Signed-off-by: Yinan Wang <yinan.wang@intel.com>
---
 test_plans/dpdk_gro_lib_test_plan.rst | 43 +++++++++++++++++----------
 1 file changed, 27 insertions(+), 16 deletions(-)

diff --git a/test_plans/dpdk_gro_lib_test_plan.rst b/test_plans/dpdk_gro_lib_test_plan.rst
index 410ae68..1ec8c23 100644
--- a/test_plans/dpdk_gro_lib_test_plan.rst
+++ b/test_plans/dpdk_gro_lib_test_plan.rst
@@ -84,12 +84,31 @@ Modify the testpmd code as following::
                     parse_ethernet(eth_hdr, &info);
                     l3_hdr = (char *)eth_hdr + info.l2_len;
 
+Also modify the dpdk code as following::
+    
+    --- a/drivers/net/vhost/rte_eth_vhost.c
+    +++ b/drivers/net/vhost/rte_eth_vhost.c
+    @@ -1071,8 +1071,14 @@ eth_dev_info(struct rte_eth_dev *dev,
+    dev_info->min_rx_bufsize = 0;
+    dev_info->tx_offload_capa = DEV_TX_OFFLOAD_MULTI_SEGS |
+    -       DEV_TX_OFFLOAD_VLAN_INSERT;
+    - dev_info->rx_offload_capa = DEV_RX_OFFLOAD_VLAN_STRIP;
+    +       DEV_TX_OFFLOAD_VLAN_INSERT |
+    +       DEV_TX_OFFLOAD_UDP_CKSUM |
+    +       DEV_TX_OFFLOAD_TCP_CKSUM |
+    +       DEV_TX_OFFLOAD_IPV4_CKSUM |
+    +       DEV_TX_OFFLOAD_TCP_TSO;
+    + dev_info->rx_offload_capa = DEV_RX_OFFLOAD_VLAN_STRIP |
+    +       DEV_RX_OFFLOAD_TCP_CKSUM |
+    +       DEV_RX_OFFLOAD_UDP_CKSUM |
+    +       DEV_RX_OFFLOAD_IPV4_CKSUM |
+    +       DEV_RX_OFFLOAD_TCP_LRO;
+     }
+
 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
 =========================================================
@@ -121,9 +140,7 @@ 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 \
@@ -176,9 +193,7 @@ 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 \
@@ -231,9 +246,7 @@ 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 \
@@ -308,9 +321,7 @@ 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 \
@@ -335,4 +346,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
\ No newline at end of file
+    VM side:     iperf -s -f g
-- 
2.17.1


             reply	other threads:[~2020-08-20  1:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20 10:12 Yinan Wang [this message]
2020-08-21 11:28 Yinan Wang
2020-09-21 10:02 Yinan Wang
2020-10-12  7:59 ` Tu, Lijuan
2020-11-04 12:13 Yinan Wang
2020-11-11  3:23 ` 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=20200820101246.15902-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).