* [dts] [PATCH V1] Add test plan about vhost qemu mtu
@ 2018-04-10 6:31 lihong
0 siblings, 0 replies; 10+ messages in thread
From: lihong @ 2018-04-10 6:31 UTC (permalink / raw)
To: dts; +Cc: lihong
Signed-off-by: lihong <lihongx.ma@intel.com>
---
test_plans/vhost_qemu_mtu_test_plan.rst | 146 ++++++++++++++++++++++++++++++++
1 file changed, 146 insertions(+)
create mode 100644 test_plans/vhost_qemu_mtu_test_plan.rst
diff --git a/test_plans/vhost_qemu_mtu_test_plan.rst b/test_plans/vhost_qemu_mtu_test_plan.rst
new file mode 100644
index 0000000..0f0dab8
--- /dev/null
+++ b/test_plans/vhost_qemu_mtu_test_plan.rst
@@ -0,0 +1,146 @@
+.. Copyright (c) <2018>, 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.
+
+===================
+Vhost MTU Test Plan
+===================
+
+The feature test the setting of MTU value of virtio-net and kernel driver.
+
+Prerequisites:
+==============
+
+The guests kernel should grand than 4.10
+The qemu version should greater or equal to 2.9
+
+The MTU length is the length of Ether content, so the packet length is
+MTU + length of Ether(not include CRC).
+Test the MTU function, we send the packet size with:
+packet length < MTU + len(Ether)
+packek length = MTU + len(Ether)
+packet length > MTU + len(Ether)
+When the packet length less or equal to the MTU value + length of Ether,
+the testpmd can received the packet.
+And when the packet length greater than the MTU value + length of Ether,
+the testpmd can not recevied the packet.
+
+Test Case: Test the MTU in virtio-net
+=====================================
+1. Launch the testpmd by below commands on host, and config mtu::
+
+ ./testpmd -c 0xc -n 4 --socket-mem 2048,2048 \
+ --vdev 'net_vhost0,iface=vhost-net,queues=1' \
+ -- -i --txd=512 --rxd=128 --nb-cores=1 --port-topology=chained
+ testpmd> port config mtu 0 2000
+ testpmd> set fwd mac
+ testpmd> start
+
+2. Launch VM::
+
+ Use the qemu_2.9 or qemu 2.10 to start the VM and the VM kernel should
+ grand than 4.10, set the mtu value to 2000
+
+ qemu-system-x86_64 \
+ -chardev socket,id=char0,path=./vhost-net \
+ -netdev type=vhost-user,id=netdev0,chardev=char0,vhostforce \
+ -device virtio-net-pci,netdev=netdev0,mrg_rxbuf=on,host_mtu=2000
+
+3. Check the MTU value in VM::
+
+ Use the ifconfig command to check the MTU value of
+ virtio kernel driver is 2000 in VM.
+
+4. Use scapy to listen on virtio driver::
+ >>> sniff(iface="ens4", count=1)
+
+5. Send a packet with size 1014, smaller than MTU + len(Ether)::
+
+ The vm can receive the packet.
+
+6. Send a packet with size 2014, equal to MTU + len(Ether)::
+
+ The vm can receive the packet.
+
+7. Send a packet with size 2015, greater than MTU + len(Ether)::
+
+ The vm can not receive the packet.
+
+8. Exit the scapy.
+
+Test Case: Test the MTU in pmd
+==============================
+1. Continue use the VM in Test Case1, bind the kernel driver to igb_uio::
+
+2. Launch testpmd in VM::
+
+ ./testpmd -c 0x03 -n 3 \
+ -- -i --txd=512 --rxd=128 --tx-offloads=0x0 --enable-hw-vlan-strip
+ testpmd> set fwd mac
+ testpmd> start
+
+3. Run `show port info 0` in VM, and check the MTU value is equal to 2000.
+
+4. Send a packet with size 1014, smaller than MTU + len(Ether)::
+ testpmd> clear port stats all
+ testpmd> show port stats 0
+
+ ######################## NIC statistics for port 0 #######################
+ RX-packets: 1 RX-missed: 0 RX-bytes: 1014
+ RX-errors: 0
+ RX-nombuf: 0
+ TX-packets: 1 TX-errors: 0 TX-bytes: 1014
+
+ Throughput (since last show)
+ Rx-pps: 0
+ Tx-pps: 0
+ ###########################################################################
+
+5. Send a packet with size 2014, equal to MTU + len(Ether)::
+ testpmd> clear port stats all
+ testpmd> show port stats 0
+
+ ######################## NIC statistics for port 0 #######################
+ RX-packets: 1 RX-missed: 0 RX-bytes: 2014
+ RX-errors: 0
+ RX-nombuf: 0
+ RX-packets: 1 TX-errors: 0 TX-bytes: 2014
+
+ Throughput (since last show)
+ Rx-pps: 0
+ Tx-pps: 0
+ ###########################################################################
+
+6. Send a packet with size 2015, greater than MTU + len(Ether)::
+ testpmd> clear port stats all
+ testpmd> show port stats 0
+
+ The testpmd can not received the packet.
--
2.7.4
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [dts] [PATCH V1] Add test plan about vhost qemu mtu
2018-04-10 8:09 lihong
@ 2018-04-16 13:16 ` Liu, Yong
0 siblings, 0 replies; 10+ messages in thread
From: Liu, Yong @ 2018-04-16 13:16 UTC (permalink / raw)
To: lihong, dts
Thanks, lihong. Applied in.
On 06/20/2020 03:06 AM, lihong wrote:
> Signed-off-by: lihong<lihongx.ma@intel.com>
^ permalink raw reply [flat|nested] 10+ messages in thread
* [dts] [PATCH V1] Add test plan about vhost qemu mtu
@ 2018-04-10 8:09 lihong
2018-04-16 13:16 ` Liu, Yong
0 siblings, 1 reply; 10+ messages in thread
From: lihong @ 2018-04-10 8:09 UTC (permalink / raw)
To: dts; +Cc: lihong
Signed-off-by: lihong <lihongx.ma@intel.com>
---
test_plans/vhost_qemu_mtu_test_plan.rst | 83 +++++++++++++++++++++++++++++++++
1 file changed, 83 insertions(+)
create mode 100644 test_plans/vhost_qemu_mtu_test_plan.rst
diff --git a/test_plans/vhost_qemu_mtu_test_plan.rst b/test_plans/vhost_qemu_mtu_test_plan.rst
new file mode 100644
index 0000000..d7f01ee
--- /dev/null
+++ b/test_plans/vhost_qemu_mtu_test_plan.rst
@@ -0,0 +1,83 @@
+.. Copyright (c) <2018>, 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.
+
+===================
+Vhost MTU Test Plan
+===================
+
+The feature test the setting of MTU value of virtio-net and kernel driver.
+
+Prerequisites:
+==============
+
+The guests kernel should grand than 4.10
+The qemu version should greater or equal to 2.9
+
+Test Case: Test the MTU in virtio-net
+=====================================
+1. Launch the testpmd by below commands on host, and config mtu::
+
+ ./testpmd -c 0xc -n 4 --socket-mem 2048,2048 \
+ --vdev 'net_vhost0,iface=vhost-net,queues=1' \
+ -- -i --txd=512 --rxd=128 --nb-cores=1 --port-topology=chained
+ testpmd> set fwd mac
+ testpmd> start
+
+2. Launch VM::
+
+ Use the qemu_2.9 or qemu 2.10 to start the VM and the VM kernel should
+ grand than 4.10, set the mtu value to 9000
+
+ qemu-system-x86_64 \
+ -chardev socket,id=char0,path=./vhost-net \
+ -netdev type=vhost-user,id=netdev0,chardev=char0,vhostforce \
+ -device virtio-net-pci,netdev=netdev0,mrg_rxbuf=on,host_mtu=9000
+
+3. Check the MTU value in VM::
+
+ Use the ifconfig command to check the MTU value of
+ virtio kernel driver is 9000 in VM.
+
+4. Bind the virtio driver to igb_uio, launch testpmd in VM, and verify
+ the mtu in port info is 9000::
+
+ ./testpmd -c 0x03 -n 3 \
+ -- -i --txd=512 --rxd=128 --tx-offloads=0x0 --enable-hw-vlan-strip
+ testpmd> set fwd mac
+ testpmd> start
+ testpmd> show port info 0
+
+5. Check the MTU value of virtio in testpmd on host is 9000::
+ testpmd> show port info 1
+
+6. Repeat the step 2 ~ 5, change the mtu value to 68, 65535(the minimal value
+ and maximum value), verify the value is changed.
--
2.7.4
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [dts] [PATCH V1] Add test plan about vhost qemu mtu
2018-03-29 0:48 lihong
@ 2018-04-04 5:15 ` Liu, Yong
0 siblings, 0 replies; 10+ messages in thread
From: Liu, Yong @ 2018-04-04 5:15 UTC (permalink / raw)
To: Ma, LihongX, dts; +Cc: Ma, LihongX
Lihong,
Some comments are inline.
Thanks,
Marvin
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of lihong
> Sent: Thursday, March 29, 2018 8:49 AM
> To: dts@dpdk.org
> Cc: Ma, LihongX <lihongx.ma@intel.com>
> Subject: [dts] [PATCH V1] Add test plan about vhost qemu mtu
>
> Signed-off-by: lihong <lihongx.ma@intel.com>
> ---
> test_plans/vhost_qemu_mtu_test_plan.rst | 139
> ++++++++++++++++++++++++++++++++
> 1 file changed, 139 insertions(+)
> create mode 100644 test_plans/vhost_qemu_mtu_test_plan.rst
>
> diff --git a/test_plans/vhost_qemu_mtu_test_plan.rst
> b/test_plans/vhost_qemu_mtu_test_plan.rst
> new file mode 100644
> index 0000000..26300b7
> --- /dev/null
> +++ b/test_plans/vhost_qemu_mtu_test_plan.rst
> @@ -0,0 +1,139 @@
> +.. Copyright (c) <2018>, 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.
> +
> +===================
> +Vhost TSO Test Plan
> +===================
Why here is TSO?
> +
> +The feature test the setting of MTU value of virtio-net and kernel driver.
> +
> +Prerequisites:
> +==============
> +
> +The guests kernel should grand than 4.10
> +The qemu version should greater or equal to 2.9
> +
> +Test Case: Test the MTU in virtio-net
> +=====================================
> +1. Launch the tetspmd by below commands on host::
Typo here.
> +
> + ./testpmd -c 0xc -n 4 --socket-mem 2048,2048 \
> + --vdev 'net_vhost0,iface=vhost-net,queues=1' \
> + -- -i --txd=512 --rxd=128 --nb-cores=1 --port-topology=chained
> + testpmd> set fwd mac
> + testpmd> start
Should MTU value setting command be here?
> +
> +2. Launch VM::
> +
> + Use the qemu_2.9 or qemu 2.10 to start the VM and the VM kernel
> should
> + grand than 4.10, set the mtu value to 1472
> +
> + taskset -c 4,5 qemu-system-x86_64 -name vm0 -enable-kvm \
> + -chardev socket,path=/tmp/vm0_qga0.sock,server,nowait,id=vm0_qga0 \
> + -device virtio-serial -device
> virtserialport,chardev=vm0_qga0,name=org.qemu.guest_agent.0 \
> + -daemonize -monitor unix:/tmp/vm0_monitor.sock,server,nowait \
> + -chardev socket,id=char0,path=./vhost-net -netdev type=vhost-
> user,id=netdev0,chardev=char0,vhostforce \
> + -device virtio-net-
> pci,netdev=netdev0,mac=52:54:00:00:00:01,mrg_rxbuf=on,host_mtu=1472 \
> + -cpu host -smp 4 -m 2048 -object memory-backend-
> file,id=mem,size=2048M,mem-path=/mnt/huge,share=on \
> + -numa node,memdev=mem -mem-prealloc -drive file=/home/osimg/ubuntu-
> ker-410.img -vnc :4
Do not need to attach command here, just few import information is enough like:
qemu-system-x86_64 \
-chardev socket,id=char0,path=./vhost-net \
-netdev type=vhost-user,id=netdev0,chardev=char0,vhostforce \
-device virtio-net- pci,netdev=netdev0,mrg_rxbuf=on,host_mtu=$MTU
> +
> +3. Check the MTU value in VM::
> +
> + Use the ifconfig command to check the MTU value of
> + virtio kernel driver is 1472 in VM.
> +
Please also do function check here. I think two cases in this test plan is enough.
One is MTU with virtio user pmd.
Another is MTU with virtio net driver.
> +Test Case: Test the MTU in pmd
> +==============================
> +1. Continue use the VM in Test Case1, bind the kernel driver to igb_uio::
> +
> +2. Launch testpmd in VM::
> +
> + ./testpmd -c 0x03 -n 3 \
> + -- -i --txd=512 --rxd=128 --tx-offloads=0x0 --enable-hw-vlan-strip
> + testpmd> set fwd mac
> + testpmd> start
> +
> +3. Run `show port info 0` in VM, and check the MTU value is equal to 1472.
> +
> +Test Case: Test the function about MTU
> +======================================
> +This case is to check if the testpmd can receive and forward the packet
> after
> +change the mtu value. Send the IP packet and the packet size smaller than
> MTU
> +value, equal to MTU value, greater than MTU value, check the testpmd can
> receive
> +and forward all the packet.
> +
> +1. Continue use the VM in Test Case2.
> +
> +2. Send a IP packet with size 1470, samller than MTU value::
Typo here.
MTU is not the concept of packet length, it is the length of Ether content.
Packet length should be 1470 + 18.
> + testpmd> clear port stats all
> + testpmd> show port stats 0
> +
> + ######################## NIC statistics for port 0
> #######################
> + RX-packets: 1 RX-missed: 0 RX-bytes: 1470
> + RX-errors: 0
> + RX-nombuf: 0
> + TX-packets: 1 TX-errors: 0 TX-bytes: 1470
> +
> + Throughput (since last show)
> + Rx-pps: 0
> + Tx-pps: 0
> +
> ##########################################################################
> #
> +
> +3. Send a IP packet with size 1472, equal to MTU value::
> + testpmd> clear port stats all
> + testpmd> show port stats 0
> +
> + ######################## NIC statistics for port 0
> #######################
> + RX-packets: 1 RX-missed: 0 RX-bytes: 1472
> + RX-errors: 0
> + RX-nombuf: 0
> + RX-packets: 1 TX-errors: 0 TX-bytes: 1472
> +
> + Throughput (since last show)
> + Rx-pps: 0
> + Tx-pps: 0
> +
> ##########################################################################
> #
> +
> +4. Send a IP packet with size 1500, greater than MTU value::
> + testpmd> clear port stats all
> + testpmd> show port stats 0
> +
> + ######################## NIC statistics for port 0
> #######################
> + RX-packets: 1 RX-missed: 0 RX-bytes: 1500
> + RX-errors: 0
> + RX-nombuf: 0
> + TX-packets: 1 TX-errors: 0 TX-bytes: 1500
> +
> + Throughput (since last show)
> + Rx-pps: 0
> + Tx-pps: 0
> +
> ##########################################################################
> #
When packet size is over MTU, still can receive packet? I think that's not the concept of MTU, please check it.
> --
> 2.7.4
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [dts] [PATCH V1] Add test plan about vhost qemu mtu
2018-03-28 18:32 lihong
@ 2018-03-29 2:42 ` Liu, Yong
0 siblings, 0 replies; 10+ messages in thread
From: Liu, Yong @ 2018-03-29 2:42 UTC (permalink / raw)
To: Ma, LihongX, dts; +Cc: Ma, LihongX
Lihong,
Please also check functionality of MTU, you can reference to jumbo frame test plan.
http://dpdk.org/doc/dts/test_plans/jumboframes_test_plan.html
Thanks,
Marvin
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of lihong
> Sent: Thursday, March 29, 2018 2:32 AM
> To: dts@dpdk.org
> Cc: Ma, LihongX <lihongx.ma@intel.com>
> Subject: [dts] [PATCH V1] Add test plan about vhost qemu mtu
>
> Signed-off-by: lihong <lihongx.ma@intel.com>
> ---
> test_plans/vhost_qemu_mtu_test_plan.rst | 88
> +++++++++++++++++++++++++++++++++
> 1 file changed, 88 insertions(+)
> create mode 100644 test_plans/vhost_qemu_mtu_test_plan.rst
>
> diff --git a/test_plans/vhost_qemu_mtu_test_plan.rst
> b/test_plans/vhost_qemu_mtu_test_plan.rst
> new file mode 100644
> index 0000000..f53bdfd
> --- /dev/null
> +++ b/test_plans/vhost_qemu_mtu_test_plan.rst
> @@ -0,0 +1,88 @@
> +.. Copyright (c) <2018>, 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.
> +
> +===================
> +Vhost TSO Test Plan
> +===================
> +
> +The feature test the setting of MTU value of virtio-net and kernel driver.
> +
> +Prerequisites:
> +==============
> +
> +The guests kernel should grand than 4.10
> +The qemu version should greater or equal to 2.9
> +
> +Test Case: Test the MTU in virtio-net
> +=====================================
> +1. Launch the tetspmd by below commands on host::
> +
> + ./testpmd -c 0xc -n 4 --socket-mem 2048,2048 \
> + --vdev 'net_vhost0,iface=vhost-net,queues=1' \
> + -- -i --txd=512 --rxd=128 --nb-cores=1 --port-topology=chained
> + testpmd> set fwd mac
> + testpmd> start
> +
> +2. Launch VM::
> +
> + Use the qemu_2.9 or qemu 2.10 to start the VM and the VM kernel
> should
> + grand than 4.10, set the mtu value to 9000
> +
> + taskset -c 4,5 qemu-system-x86_64 -name vm0 -enable-kvm \
> + -chardev socket,path=/tmp/vm0_qga0.sock,server,nowait,id=vm0_qga0 \
> + -device virtio-serial -device
> virtserialport,chardev=vm0_qga0,name=org.qemu.guest_agent.0 \
> + -daemonize -monitor unix:/tmp/vm0_monitor.sock,server,nowait \
> + -chardev socket,id=char0,path=./vhost-net -netdev type=vhost-
> user,id=netdev0,chardev=char0,vhostforce \
> + -device virtio-net-
> pci,netdev=netdev0,mac=52:54:00:00:00:01,mrg_rxbuf=on,host_mtu=9000 \
> + -cpu host -smp 4 -m 2048 -object memory-backend-
> file,id=mem,size=2048M,mem-path=/mnt/huge,share=on \
> + -numa node,memdev=mem -mem-prealloc -drive file=/home/osimg/ubuntu-
> ker-410.img -vnc :4
> +
> +3. Check the MTU value in VM::
> +
> + Use the ifconfig command to check the MTU value of
> + virtio kernel driver is 9000 in VM.
> +
> +Test Case: Test the MTU in pmd
> +==============================
> +
> +1. Continue use the VM in Test Case1, bind the kernel driver to igb_uio::
> +
> +2. Launch testpmd in VM::
> +
> + ./testpmd -c 0x03 -n 3 \
> + -- -i --txd=512 --rxd=128 --tx-offloads=0x0 --enable-hw-vlan-strip
> + testpmd> set fwd mac
> + testpmd> start
> +
> +3. Run `show port info 0` in VM, and check the MTU value is equal to 9000,
> + start packet generator to transmit and receive packets, and check if
> + testpmd is able to receive and forward packets
> --
> 2.7.4
^ permalink raw reply [flat|nested] 10+ messages in thread
* [dts] [PATCH V1] Add test plan about vhost qemu mtu
@ 2018-03-29 0:48 lihong
2018-04-04 5:15 ` Liu, Yong
0 siblings, 1 reply; 10+ messages in thread
From: lihong @ 2018-03-29 0:48 UTC (permalink / raw)
To: dts; +Cc: lihong
Signed-off-by: lihong <lihongx.ma@intel.com>
---
test_plans/vhost_qemu_mtu_test_plan.rst | 139 ++++++++++++++++++++++++++++++++
1 file changed, 139 insertions(+)
create mode 100644 test_plans/vhost_qemu_mtu_test_plan.rst
diff --git a/test_plans/vhost_qemu_mtu_test_plan.rst b/test_plans/vhost_qemu_mtu_test_plan.rst
new file mode 100644
index 0000000..26300b7
--- /dev/null
+++ b/test_plans/vhost_qemu_mtu_test_plan.rst
@@ -0,0 +1,139 @@
+.. Copyright (c) <2018>, 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.
+
+===================
+Vhost TSO Test Plan
+===================
+
+The feature test the setting of MTU value of virtio-net and kernel driver.
+
+Prerequisites:
+==============
+
+The guests kernel should grand than 4.10
+The qemu version should greater or equal to 2.9
+
+Test Case: Test the MTU in virtio-net
+=====================================
+1. Launch the tetspmd by below commands on host::
+
+ ./testpmd -c 0xc -n 4 --socket-mem 2048,2048 \
+ --vdev 'net_vhost0,iface=vhost-net,queues=1' \
+ -- -i --txd=512 --rxd=128 --nb-cores=1 --port-topology=chained
+ testpmd> set fwd mac
+ testpmd> start
+
+2. Launch VM::
+
+ Use the qemu_2.9 or qemu 2.10 to start the VM and the VM kernel should
+ grand than 4.10, set the mtu value to 1472
+
+ taskset -c 4,5 qemu-system-x86_64 -name vm0 -enable-kvm \
+ -chardev socket,path=/tmp/vm0_qga0.sock,server,nowait,id=vm0_qga0 \
+ -device virtio-serial -device virtserialport,chardev=vm0_qga0,name=org.qemu.guest_agent.0 \
+ -daemonize -monitor unix:/tmp/vm0_monitor.sock,server,nowait \
+ -chardev socket,id=char0,path=./vhost-net -netdev type=vhost-user,id=netdev0,chardev=char0,vhostforce \
+ -device virtio-net-pci,netdev=netdev0,mac=52:54:00:00:00:01,mrg_rxbuf=on,host_mtu=1472 \
+ -cpu host -smp 4 -m 2048 -object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on \
+ -numa node,memdev=mem -mem-prealloc -drive file=/home/osimg/ubuntu-ker-410.img -vnc :4
+
+3. Check the MTU value in VM::
+
+ Use the ifconfig command to check the MTU value of
+ virtio kernel driver is 1472 in VM.
+
+Test Case: Test the MTU in pmd
+==============================
+1. Continue use the VM in Test Case1, bind the kernel driver to igb_uio::
+
+2. Launch testpmd in VM::
+
+ ./testpmd -c 0x03 -n 3 \
+ -- -i --txd=512 --rxd=128 --tx-offloads=0x0 --enable-hw-vlan-strip
+ testpmd> set fwd mac
+ testpmd> start
+
+3. Run `show port info 0` in VM, and check the MTU value is equal to 1472.
+
+Test Case: Test the function about MTU
+======================================
+This case is to check if the testpmd can receive and forward the packet after
+change the mtu value. Send the IP packet and the packet size smaller than MTU
+value, equal to MTU value, greater than MTU value, check the testpmd can receive
+and forward all the packet.
+
+1. Continue use the VM in Test Case2.
+
+2. Send a IP packet with size 1470, samller than MTU value::
+ testpmd> clear port stats all
+ testpmd> show port stats 0
+
+ ######################## NIC statistics for port 0 #######################
+ RX-packets: 1 RX-missed: 0 RX-bytes: 1470
+ RX-errors: 0
+ RX-nombuf: 0
+ TX-packets: 1 TX-errors: 0 TX-bytes: 1470
+
+ Throughput (since last show)
+ Rx-pps: 0
+ Tx-pps: 0
+ ###########################################################################
+
+3. Send a IP packet with size 1472, equal to MTU value::
+ testpmd> clear port stats all
+ testpmd> show port stats 0
+
+ ######################## NIC statistics for port 0 #######################
+ RX-packets: 1 RX-missed: 0 RX-bytes: 1472
+ RX-errors: 0
+ RX-nombuf: 0
+ RX-packets: 1 TX-errors: 0 TX-bytes: 1472
+
+ Throughput (since last show)
+ Rx-pps: 0
+ Tx-pps: 0
+ ###########################################################################
+
+4. Send a IP packet with size 1500, greater than MTU value::
+ testpmd> clear port stats all
+ testpmd> show port stats 0
+
+ ######################## NIC statistics for port 0 #######################
+ RX-packets: 1 RX-missed: 0 RX-bytes: 1500
+ RX-errors: 0
+ RX-nombuf: 0
+ TX-packets: 1 TX-errors: 0 TX-bytes: 1500
+
+ Throughput (since last show)
+ Rx-pps: 0
+ Tx-pps: 0
+ ###########################################################################
--
2.7.4
^ permalink raw reply [flat|nested] 10+ messages in thread
* [dts] [PATCH V1] Add test plan about vhost qemu mtu
@ 2018-03-28 18:32 lihong
2018-03-29 2:42 ` Liu, Yong
0 siblings, 1 reply; 10+ messages in thread
From: lihong @ 2018-03-28 18:32 UTC (permalink / raw)
To: dts; +Cc: lihong
Signed-off-by: lihong <lihongx.ma@intel.com>
---
test_plans/vhost_qemu_mtu_test_plan.rst | 88 +++++++++++++++++++++++++++++++++
1 file changed, 88 insertions(+)
create mode 100644 test_plans/vhost_qemu_mtu_test_plan.rst
diff --git a/test_plans/vhost_qemu_mtu_test_plan.rst b/test_plans/vhost_qemu_mtu_test_plan.rst
new file mode 100644
index 0000000..f53bdfd
--- /dev/null
+++ b/test_plans/vhost_qemu_mtu_test_plan.rst
@@ -0,0 +1,88 @@
+.. Copyright (c) <2018>, 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.
+
+===================
+Vhost TSO Test Plan
+===================
+
+The feature test the setting of MTU value of virtio-net and kernel driver.
+
+Prerequisites:
+==============
+
+The guests kernel should grand than 4.10
+The qemu version should greater or equal to 2.9
+
+Test Case: Test the MTU in virtio-net
+=====================================
+1. Launch the tetspmd by below commands on host::
+
+ ./testpmd -c 0xc -n 4 --socket-mem 2048,2048 \
+ --vdev 'net_vhost0,iface=vhost-net,queues=1' \
+ -- -i --txd=512 --rxd=128 --nb-cores=1 --port-topology=chained
+ testpmd> set fwd mac
+ testpmd> start
+
+2. Launch VM::
+
+ Use the qemu_2.9 or qemu 2.10 to start the VM and the VM kernel should
+ grand than 4.10, set the mtu value to 9000
+
+ taskset -c 4,5 qemu-system-x86_64 -name vm0 -enable-kvm \
+ -chardev socket,path=/tmp/vm0_qga0.sock,server,nowait,id=vm0_qga0 \
+ -device virtio-serial -device virtserialport,chardev=vm0_qga0,name=org.qemu.guest_agent.0 \
+ -daemonize -monitor unix:/tmp/vm0_monitor.sock,server,nowait \
+ -chardev socket,id=char0,path=./vhost-net -netdev type=vhost-user,id=netdev0,chardev=char0,vhostforce \
+ -device virtio-net-pci,netdev=netdev0,mac=52:54:00:00:00:01,mrg_rxbuf=on,host_mtu=9000 \
+ -cpu host -smp 4 -m 2048 -object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on \
+ -numa node,memdev=mem -mem-prealloc -drive file=/home/osimg/ubuntu-ker-410.img -vnc :4
+
+3. Check the MTU value in VM::
+
+ Use the ifconfig command to check the MTU value of
+ virtio kernel driver is 9000 in VM.
+
+Test Case: Test the MTU in pmd
+==============================
+
+1. Continue use the VM in Test Case1, bind the kernel driver to igb_uio::
+
+2. Launch testpmd in VM::
+
+ ./testpmd -c 0x03 -n 3 \
+ -- -i --txd=512 --rxd=128 --tx-offloads=0x0 --enable-hw-vlan-strip
+ testpmd> set fwd mac
+ testpmd> start
+
+3. Run `show port info 0` in VM, and check the MTU value is equal to 9000,
+ start packet generator to transmit and receive packets, and check if
+ testpmd is able to receive and forward packets
--
2.7.4
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [dts] [PATCH V1] Add test plan about vhost qemu mtu
2018-03-23 6:24 lihong
2018-03-27 9:04 ` Liu, Yong
@ 2018-03-28 0:17 ` Ferruh Yigit
1 sibling, 0 replies; 10+ messages in thread
From: Ferruh Yigit @ 2018-03-28 0:17 UTC (permalink / raw)
To: lihong, dts; +Cc: Qian Xu
On 4/28/2020 5:34 PM, lihong wrote:
> Signed-off-by: lihong <lihongx.ma@intel.com>
This mail is coming from 4 April 2020 :)
You may consider to update time in your box.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [dts] [PATCH V1] Add test plan about vhost qemu mtu
2018-03-23 6:24 lihong
@ 2018-03-27 9:04 ` Liu, Yong
2018-03-28 0:17 ` Ferruh Yigit
1 sibling, 0 replies; 10+ messages in thread
From: Liu, Yong @ 2018-03-27 9:04 UTC (permalink / raw)
To: Ma, LihongX, dts; +Cc: Ma, LihongX
Lihong,
Some comments are inline.
Thanks
Marvin
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of lihong
> Sent: Wednesday, April 29, 2020 12:35 AM
> To: dts@dpdk.org
> Cc: Ma, LihongX <lihongx.ma@intel.com>
> Subject: [dts] [PATCH V1] Add test plan about vhost qemu mtu
>
> Signed-off-by: lihong <lihongx.ma@intel.com>
> ---
> test_plans/vhost_qemu_mtu_test_plan.rst | 82
> +++++++++++++++++++++++++++++++++
> 1 file changed, 82 insertions(+)
> create mode 100644 test_plans/vhost_qemu_mtu_test_plan.rst
>
> diff --git a/test_plans/vhost_qemu_mtu_test_plan.rst
> b/test_plans/vhost_qemu_mtu_test_plan.rst
> new file mode 100644
> index 0000000..3c9c0ab
> --- /dev/null
> +++ b/test_plans/vhost_qemu_mtu_test_plan.rst
> @@ -0,0 +1,82 @@
> +.. Copyright (c) <2018>, 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.
> +
> +===================
> +Vhost TSO Test Plan
> +===================
> +
> +The feature test the setting of MTU value of virtio-net and kernel driver.
> +
> +Prerequisites:
> +==============
> +
> +The guests kernel should grand than 4.10
> +The qemu version should greater or equal to 2.9
> +
> +Test Case: Test kernel driver in guests
> +=======================================
> +1. Launch the tetspmd by below commands on host::
> +
> + ./testpmd -c 0xc -n 4 --socket-mem 2048,2048 \
> + --vdev 'net_vhost0,iface=vhost-net,queues=1' \
> + -- -i --txd=512 --rxd=128 --nb-cores=1 --port-topology=chained
> +
> +2. Launch VM::
> +
> + Use the qemu_2.9 or qemu 2.10 to start the VM and the VM kernel
> should
> + grand than 4.10, set the mtu value to 8888
Please use reasonable MTU setting, like 68, 1500, 9000.
> +
> + taskset -c 4,5 qemu-system-x86_64 -name vm0 -enable-kvm \
> + -chardev socket,path=/tmp/vm0_qga0.sock,server,nowait,id=vm0_qga0 \
> + -device virtio-serial -device
> virtserialport,chardev=vm0_qga0,name=org.qemu.guest_agent.0 \
> + -daemonize -monitor unix:/tmp/vm0_monitor.sock,server,nowait \
> + -chardev socket,id=char0,path=./vhost-net -netdev type=vhost-
> user,id=netdev0,chardev=char0,vhostforce \
> + -device virtio-net-
> pci,netdev=netdev0,mac=52:54:00:00:00:01,mrg_rxbuf=on,host_mtu=8888 \
> + -cpu host -smp 4 -m 2048 -object memory-backend-
> file,id=mem,size=2048M,mem-path=/mnt/huge,share=on \
> + -numa node,memdev=mem -mem-prealloc -drive file=/home/osimg/ubuntu-
> ker-410.img -vnc :4
> +
> +3. Check the MTU value in VM::
> +
> + Use the ifconfig command to check the MTU value of
> + virtio kernel driver is 8888 in VM.
> +
> +Test Case: Test the virtio-net MTU
> +==================================
Please change case name format, use name like "MTU in pmd" and "MTU in virtio-net".
Here I only saw basic output check, I think still need function test here.
> +
> +1. Continue use the VM in Test Case1, bind the kernel driver to igb_uio::
> +
> +2. Launch testpmd in VM::
> +
> + ./testpmd -c 0x03 -n 3 \
> + -- -i --txd=512 --rxd=128 --tx-offloads=0x0 --enable-hw-vlan-strip
> +
> +3. Run `show port info 0` in VM, and check the MTU value is equal to 8888
> --
> 2.7.4
^ permalink raw reply [flat|nested] 10+ messages in thread
* [dts] [PATCH V1] Add test plan about vhost qemu mtu
@ 2018-03-23 6:24 lihong
2018-03-27 9:04 ` Liu, Yong
2018-03-28 0:17 ` Ferruh Yigit
0 siblings, 2 replies; 10+ messages in thread
From: lihong @ 2018-03-23 6:24 UTC (permalink / raw)
To: dts; +Cc: lihong
Signed-off-by: lihong <lihongx.ma@intel.com>
---
test_plans/vhost_qemu_mtu_test_plan.rst | 82 +++++++++++++++++++++++++++++++++
1 file changed, 82 insertions(+)
create mode 100644 test_plans/vhost_qemu_mtu_test_plan.rst
diff --git a/test_plans/vhost_qemu_mtu_test_plan.rst b/test_plans/vhost_qemu_mtu_test_plan.rst
new file mode 100644
index 0000000..3c9c0ab
--- /dev/null
+++ b/test_plans/vhost_qemu_mtu_test_plan.rst
@@ -0,0 +1,82 @@
+.. Copyright (c) <2018>, 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.
+
+===================
+Vhost TSO Test Plan
+===================
+
+The feature test the setting of MTU value of virtio-net and kernel driver.
+
+Prerequisites:
+==============
+
+The guests kernel should grand than 4.10
+The qemu version should greater or equal to 2.9
+
+Test Case: Test kernel driver in guests
+=======================================
+1. Launch the tetspmd by below commands on host::
+
+ ./testpmd -c 0xc -n 4 --socket-mem 2048,2048 \
+ --vdev 'net_vhost0,iface=vhost-net,queues=1' \
+ -- -i --txd=512 --rxd=128 --nb-cores=1 --port-topology=chained
+
+2. Launch VM::
+
+ Use the qemu_2.9 or qemu 2.10 to start the VM and the VM kernel should
+ grand than 4.10, set the mtu value to 8888
+
+ taskset -c 4,5 qemu-system-x86_64 -name vm0 -enable-kvm \
+ -chardev socket,path=/tmp/vm0_qga0.sock,server,nowait,id=vm0_qga0 \
+ -device virtio-serial -device virtserialport,chardev=vm0_qga0,name=org.qemu.guest_agent.0 \
+ -daemonize -monitor unix:/tmp/vm0_monitor.sock,server,nowait \
+ -chardev socket,id=char0,path=./vhost-net -netdev type=vhost-user,id=netdev0,chardev=char0,vhostforce \
+ -device virtio-net-pci,netdev=netdev0,mac=52:54:00:00:00:01,mrg_rxbuf=on,host_mtu=8888 \
+ -cpu host -smp 4 -m 2048 -object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on \
+ -numa node,memdev=mem -mem-prealloc -drive file=/home/osimg/ubuntu-ker-410.img -vnc :4
+
+3. Check the MTU value in VM::
+
+ Use the ifconfig command to check the MTU value of
+ virtio kernel driver is 8888 in VM.
+
+Test Case: Test the virtio-net MTU
+==================================
+
+1. Continue use the VM in Test Case1, bind the kernel driver to igb_uio::
+
+2. Launch testpmd in VM::
+
+ ./testpmd -c 0x03 -n 3 \
+ -- -i --txd=512 --rxd=128 --tx-offloads=0x0 --enable-hw-vlan-strip
+
+3. Run `show port info 0` in VM, and check the MTU value is equal to 8888
--
2.7.4
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2018-04-16 5:28 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-04-10 6:31 [dts] [PATCH V1] Add test plan about vhost qemu mtu lihong
-- strict thread matches above, loose matches on Subject: below --
2018-04-10 8:09 lihong
2018-04-16 13:16 ` Liu, Yong
2018-03-29 0:48 lihong
2018-04-04 5:15 ` Liu, Yong
2018-03-28 18:32 lihong
2018-03-29 2:42 ` Liu, Yong
2018-03-23 6:24 lihong
2018-03-27 9:04 ` Liu, Yong
2018-03-28 0:17 ` Ferruh Yigit
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).