test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Wang, Yinan" <yinan.wang@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Wang, Yinan" <yinan.wang@intel.com>
Subject: Re: [dts] [PATCH v2] test_plans/dpdk_gro_lib: add test plan for dpdk	gro lib test
Date: Wed, 22 May 2019 08:41:24 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA841EF@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20190515013707.52550-1-yinan.wang@intel.com>

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Yinan
> Sent: Wednesday, May 15, 2019 9:37 AM
> To: dts@dpdk.org
> Cc: Wang, Yinan <yinan.wang@intel.com>
> Subject: [dts] [PATCH v2] test_plans/dpdk_gro_lib: add test plan for dpdk gro
> lib test
> 
> From: Wang Yinan <yinan.wang@intel.com>
> 
> ---
>  test_plans/dpdk_gro_lib_test_plan.rst | 324 ++++++++++++++++++++++++++
>  1 file changed, 324 insertions(+)
>  create mode 100644 test_plans/dpdk_gro_lib_test_plan.rst
> 
> diff --git a/test_plans/dpdk_gro_lib_test_plan.rst
> b/test_plans/dpdk_gro_lib_test_plan.rst
> new file mode 100644
> index 0000000..4ca78ef
> --- /dev/null
> +++ b/test_plans/dpdk_gro_lib_test_plan.rst
> @@ -0,0 +1,324 @@
> +.. Copyright (c) <2019>, Intel Corporation
> +   All rights reserved.
> +
> +   Redistribution and use in source and binary forms, with or without
> +   modification, are permitted provided that the following conditions
> +   are met:
> +
> +   - Redistributions of source code must retain the above copyright
> +     notice, this list of conditions and the following disclaimer.
> +
> +   - Redistributions in binary form must reproduce the above copyright
> +     notice, this list of conditions and the following disclaimer in
> +     the documentation and/or other materials provided with the
> +     distribution.
> +
> +   - Neither the name of Intel Corporation nor the names of its
> +     contributors may be used to endorse or promote products derived
> +     from this software without specific prior written permission.
> +
> +   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
> CONTRIBUTORS
> +   "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
> +   LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
> FITNESS
> +   FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
> +   COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
> INDIRECT,
> +   INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> +   (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
> OR
> +   SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
> +   HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
> CONTRACT,
> +   STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
> +   ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
> ADVISED
> +   OF THE POSSIBILITY OF SUCH DAMAGE.
> +
> +======================
> +DPDK GRO lib test plan
> +======================
> +
> +Generic Receive Offload (GRO) is a widely used SW-based offloading
> +technique to reduce per-packet processing overheads. By reassembling
> +small packets into larger ones, GRO enables applications to process
> +fewer large packets directly, thus reducing the number of packets to be
> +processed. To benefit DPDK-based applications, like Open vSwitch, DPDK
> +also provides own GRO implementation. In DPDK, GRO is implemented as a
> +standalone library. Applications explicitly use the GRO library to
> +reassemble packets.
> +
> +In the GRO library, there are many GRO types which are defined by
> +packet types. One GRO type is in charge of process one kind of packets.
> +For example, TCP/IPv4 GRO processes TCP/IPv4 packets.
> +
> +Each GRO type has a reassembly function, which defines own algorithm
> +and table structure to reassemble packets. We assign input packets to
> +the corresponding GRO functions by MBUF->packet_type.
> +
> +The GRO library doesn't check if input packets have correct checksums
> +and doesn't re-calculate checksums for merged packets. The GRO library
> +assumes the packets are complete (i.e., MF==0 && frag_off==0), when IP
> +fragmentation is possible (i.e., DF==0). Additionally, it complies RFC
> +6864 to process the IPv4 ID field.
> +
> +Currently, the GRO library provides GRO supports for TCP/IPv4 packets
> +and VxLAN packets which contain an outer IPv4 header and an inner
> +TCP/IPv4 packet.
> +
> +This test plan includes dpdk gro lib test with TCP/IPv4 traffic and
> +VxLAN traffic, also cover lightmode and heavymode test.
> +
> +Prerequisites
> +=============
> +
> +Modify the testpmd code as following::
> +
> +    --- a/app/test-pmd/csumonly.c
> +    +++ b/app/test-pmd/csumonly.c
> +    @@ -693,10 +693,12 @@ pkt_burst_checksum_forward(struct
> fwd_stream *fs)
> +                     * and inner headers */
> +
> +                    eth_hdr = rte_pktmbuf_mtod(m, struct ether_hdr *);
> +    +#if 0
> +                    ether_addr_copy(&peer_eth_addrs[fs->peer_addr],
> +                                    &eth_hdr->d_addr);
> +                    ether_addr_copy(&ports[fs->tx_port].eth_addr,
> +                                    &eth_hdr->s_addr);
> +    +#endif
> +                    parse_ethernet(eth_hdr, &info);
> +                    l3_hdr = (char *)eth_hdr + info.l2_len;
> +
> +Test flow
> +=========
> +
> +NIC2(In kernel) -> NIC1(DPDK) -> testpmd(csum fwd) -> Vhost ->
> +Virtio-net
> +
> +Test Case1: DPDK GRO lightmode test with tcp/ipv4 traffic
> +=========================================================
> +
> +1. Connect two nic port directly, put nic2 into another namesapce and turn
> on the tso of this nic port by below cmds::
> +
> +    ip netns del ns1
> +    ip netns add ns1
> +    ip link set [enp216s0f0] netns ns1       # [enp216s0f0] is the name of nic2
> +    ip netns exec ns1 ifconfig [enp216s0f0] 1.1.1.8 up
> +    ip netns exec ns1 ethtool -K [enp216s0f0] tso on
> +
> +2. Bind nic1 to igb_uio, launch vhost-user with testpmd and set flush
> interval to 1::
> +
> +    ./dpdk-devbind.py -b igb_uio xx:xx.x
> +    ./testpmd -l 2-4 -n 4 --socket-mem 1024,1024  --legacy-mem \
> +    --file-prefix=vhost --vdev 'net_vhost0,iface=vhost-net,queues=1,client=0' -
> - -i --txd=1024 --rxd=1024
> +    testpmd>set fwd csum
> +    testpmd>stop
> +    testpmd>port stop 0
> +    testpmd>port stop 1
> +    testpmd>csum set tcp hw 0
> +    testpmd>csum set ip hw 0
> +    testpmd>csum set tcp hw 1
> +    testpmd>csum set ip hw 1
> +    testpmd>set port 0 gro on
> +    testpmd>set gro flush 1
> +    testpmd>port start 0
> +    testpmd>port start 1
> +    testpmd>start
> +
> +3.  Set up vm with virto device and using kernel virtio-net driver::
> +
> +    taskset -c 13 \
> +    qemu-system-x86_64 -name us-vhost-vm1 \
> +       -cpu host -enable-kvm -m 2048 -object memory-backend-
> file,id=mem,size=2048M,mem-path=/mnt/huge,share=on \
> +       -numa node,memdev=mem \
> +       -mem-prealloc -monitor unix:/tmp/vm2_monitor.sock,server,nowait -
> net nic,vlan=2,macaddr=00:00:00:08:e8:aa,addr=1f -net
> user,vlan=2,hostfwd=tcp:127.0.0.1:6001-:22 \
> +       -smp cores=1,sockets=1 -drive file=/home/osimg/ubuntu16.img  \
> +       -chardev socket,id=char0,path=./vhost-net \
> +       -netdev type=vhost-user,id=mynet1,chardev=char0,vhostforce \
> +       -device virtio-net-
> pci,mac=52:54:00:00:00:01,netdev=mynet1,mrg_rxbuf=on,csum=on,gso=on,h
> ost_tso4=on,guest_tso4=on \
> +       -vnc :10 -daemonize
> +
> +4. In vm, config the virtio-net device with ip and turn the kernel gro off::
> +
> +    ifconfig [ens3] 1.1.1.2 up  # [ens3] is the name of virtio-net
> +    ethtool -K [ens3] gro off
> +
> +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 ns1 iperf -c 1.1.1.2 -i 1 -t 60 -m -P 1
> +    VM side:     iperf -s
> +
> +Test Case2: DPDK GRO heavymode test with tcp/ipv4 traffic
> +=========================================================
> +
> +1. Connect two nic port directly, put nic2 into another namesapce and turn
> on the tso of this nic port by below cmds::
> +
> +    ip netns del ns1
> +    ip netns add ns1
> +    ip link set [enp216s0f0] netns ns1       # [enp216s0f0] is the name of nic2
> +    ip netns exec ns1 ifconfig [enp216s0f0] 1.1.1.8 up
> +    ip netns exec ns1 ethtool -K [enp216s0f0] tso on
> +
> +2. Bind nic1 to igb_uio, launch vhost-user with testpmd and set flush
> interval to 2::
> +
> +    ./dpdk-devbind.py -b igb_uio xx:xx.x
> +    ./testpmd -l 2-4 -n 4 --socket-mem 1024,1024  --legacy-mem \
> +    --file-prefix=vhost --vdev 'net_vhost0,iface=vhost-net,queues=1,client=0' -
> - -i --txd=1024 --rxd=1024
> +    testpmd>set fwd csum
> +    testpmd>stop
> +    testpmd>port stop 0
> +    testpmd>port stop 1
> +    testpmd>csum set tcp hw 0
> +    testpmd>csum set ip hw 0
> +    testpmd>csum set tcp hw 1
> +    testpmd>csum set ip hw 1
> +    testpmd>set port 0 gro on
> +    testpmd>set gro flush 2
> +    testpmd>port start 0
> +    testpmd>port start 1
> +    testpmd>start
> +
> +3.  Set up vm with virto device and using kernel virtio-net driver::
> +
> +    taskset -c 13 \
> +    qemu-system-x86_64 -name us-vhost-vm1 \
> +       -cpu host -enable-kvm -m 2048 -object memory-backend-
> file,id=mem,size=2048M,mem-path=/mnt/huge,share=on \
> +       -numa node,memdev=mem \
> +       -mem-prealloc -monitor unix:/tmp/vm2_monitor.sock,server,nowait -
> net nic,vlan=2,macaddr=00:00:00:08:e8:aa,addr=1f -net
> user,vlan=2,hostfwd=tcp:127.0.0.1:6001-:22 \
> +       -smp cores=1,sockets=1 -drive file=/home/osimg/ubuntu16.img  \
> +       -chardev socket,id=char0,path=./vhost-net \
> +       -netdev type=vhost-user,id=mynet1,chardev=char0,vhostforce \
> +       -device virtio-net-
> pci,mac=52:54:00:00:00:01,netdev=mynet1,mrg_rxbuf=on,csum=on,gso=on,h
> ost_tso4=on,guest_tso4=on \
> +       -vnc :10 -daemonize
> +
> +4. In vm, config the virtio-net device with ip and turn the kernel gro off::
> +
> +    ifconfig [ens3] 1.1.1.2 up  # [ens3] is the name of virtio-net
> +    ethtool -K [ens3] gro off
> +
> +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 ns1 iperf -c 1.1.1.2 -i 1 -t 60 -m -P 1
> +    VM side:     iperf -s
> +
> +Test Case3: DPDK GRO heavymode_flush4 test with tcp/ipv4 traffic
> +===============================================================
> =
> +
> +1. Connect two nic port directly, put nic2 into another namesapce and turn
> on the tso of this nic port by below cmds::
> +
> +    ip netns del ns1
> +    ip netns add ns1
> +    ip link set [enp216s0f0] netns ns1       # [enp216s0f0] is the name of nic2
> +    ip netns exec ns1 ifconfig [enp216s0f0] 1.1.1.8 up
> +    ip netns exec ns1 ethtool -K [enp216s0f0] tso on
> +
> +2. Bind nic1 to igb_uio, launch vhost-user with testpmd and set flush
> interval to 4::
> +
> +    ./dpdk-devbind.py -b igb_uio xx:xx.x
> +    ./testpmd -l 2-4 -n 4 --socket-mem 1024,1024  --legacy-mem \
> +    --file-prefix=vhost --vdev 'net_vhost0,iface=vhost-net,queues=1,client=0' -
> - -i --txd=1024 --rxd=1024
> +    testpmd>set fwd csum
> +    testpmd>stop
> +    testpmd>port stop 0
> +    testpmd>port stop 1
> +    testpmd>csum set tcp hw 0
> +    testpmd>csum set ip hw 0
> +    testpmd>csum set tcp hw 1
> +    testpmd>csum set ip hw 1
> +    testpmd>set port 0 gro on
> +    testpmd>set gro flush 4
> +    testpmd>port start 0
> +    testpmd>port start 1
> +    testpmd>start
> +
> +3.  Set up vm with virto device and using kernel virtio-net driver::
> +
> +    taskset -c 13 \
> +    qemu-system-x86_64 -name us-vhost-vm1 \
> +       -cpu host -enable-kvm -m 2048 -object memory-backend-
> file,id=mem,size=2048M,mem-path=/mnt/huge,share=on \
> +       -numa node,memdev=mem \
> +       -mem-prealloc -monitor unix:/tmp/vm2_monitor.sock,server,nowait -
> net nic,vlan=2,macaddr=00:00:00:08:e8:aa,addr=1f -net
> user,vlan=2,hostfwd=tcp:127.0.0.1:6001-:22 \
> +       -smp cores=1,sockets=1 -drive file=/home/osimg/ubuntu16.img  \
> +       -chardev socket,id=char0,path=./vhost-net \
> +       -netdev type=vhost-user,id=mynet1,chardev=char0,vhostforce \
> +       -device virtio-net-
> pci,mac=52:54:00:00:00:01,netdev=mynet1,mrg_rxbuf=on,csum=on,gso=on,h
> ost_tso4=on,guest_tso4=on \
> +       -vnc :10 -daemonize
> +
> +4. In vm, config the virtio-net device with ip and turn the kernel gro off::
> +
> +    ifconfig [ens3] 1.1.1.2 up  # [ens3] is the name of virtio-net
> +    ethtool -K [ens3] gro off
> +
> +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 ns1 iperf -c 1.1.1.2 -i 1 -t 60 -m -P 1
> +    VM side:     iperf -s
> +
> +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------------|
> +
> +1. Connect two nic port directly, put nic2 into another namesapce and
> create Host VxLAN port::
> +
> +    ip netns del ns1
> +    ip netns add ns1
> +    ip link set [enp216s0f0] netns ns1    # [enp216s0f0] is the name of nic2
> +    ip netns exec ns1 ifconfig [enp216s0f0] 1.1.2.4/24 up
> +    VXLAN_NAME=vxlan1
> +    VXLAN_IP=50.1.1.1
> +    IF_NAME=[enp216s0f0]
> +    VM_IP=1.1.2.3
> +    ip netns exec t2 ip link add $VXLAN_NAME type vxlan id 42 dev
> $IF_NAME dstport 4789
> +    ip netns exec t2 bridge fdb append to 00:00:00:00:00:00 dst $VM_IP dev
> $VXLAN_NAME
> +    ip netns exec t2 ip addr add $VXLAN_IP/24 dev $VXLAN_NAME
> +    ip netns exec t2 ip link set up dev $VXLAN_NAME
> +
> +2. Bind nic1 to igb_uio, launch vhost-user with testpmd and set flush
> interval to 4::
> +
> +    ./dpdk-devbind.py -b igb_uio xx:xx.x
> +    ./testpmd -l 2-4 -n 4 --socket-mem 1024,1024  --legacy-mem \
> +    --file-prefix=vhost --vdev 'net_vhost0,iface=vhost-net,queues=1,client=0' -
> - -i --txd=1024 --rxd=1024
> +    testpmd>set fwd csum
> +    testpmd>stop
> +    testpmd>port stop 0
> +    testpmd>port stop 1
> +    testpmd>csum set tcp hw 0
> +    testpmd>csum set ip hw 0
> +    testpmd>csum parse-tunnel on 0
> +    testpmd>csum parse-tunnel on 1
> +    testpmd>csum set outer-ip hw 0
> +    testpmd>csum set tcp hw 1
> +    testpmd>csum set ip hw 1
> +    testpmd>set port 0 gro on
> +    testpmd>set gro flush 4
> +    testpmd>port start 0
> +    testpmd>port start 1
> +    testpmd>start
> +
> +3.  Set up vm with virto device and using kernel virtio-net driver::
> +
> +    taskset -c 13 \
> +    qemu-system-x86_64 -name us-vhost-vm1 \
> +       -cpu host -enable-kvm -m 2048 -object memory-backend-
> file,id=mem,size=2048M,mem-path=/mnt/huge,share=on \
> +       -numa node,memdev=mem \
> +       -mem-prealloc -monitor unix:/tmp/vm2_monitor.sock,server,nowait -
> net nic,vlan=2,macaddr=00:00:00:08:e8:aa,addr=1f -net
> user,vlan=2,hostfwd=tcp:127.0.0.1:6001-:22 \
> +       -smp cores=1,sockets=1 -drive file=/home/osimg/ubuntu16.img  \
> +       -chardev socket,id=char0,path=./vhost-net \
> +       -netdev type=vhost-user,id=mynet1,chardev=char0,vhostforce \
> +       -device virtio-net-
> pci,mac=52:54:00:00:00:01,netdev=mynet1,mrg_rxbuf=on,csum=on,gso=on,h
> ost_tso4=on,guest_tso4=on \
> +       -vnc :10 -daemonize
> +
> +4. In vm, config the virtio-net device with ip and turn the kernel gro off::
> +
> +    ip link add vxlan0 type vxlan id 42 dev [ens3] dstport 4789   # [ens3] is
> the name of virtio-net
> +    bridge fdb add to 00:00:00:00:00:00 dst 1.1.2.4 dev vxlan0
> +    ip addr add 50.1.1.2/24 dev vxlan0
> +    ip link set up dev vxlan0
> +    ifconfig [ens3] 1.1.2.3/24 up
> +    ifconfig -a
> +
> +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
> --
> 2.17.1


      reply	other threads:[~2019-05-22  8:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-15  1:37 Yinan
2019-05-22  8:41 ` Tu, Lijuan [this message]

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=8CE3E05A3F976642AAB0F4675D0AD20E0BA841EF@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=yinan.wang@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).