From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Jiang, JunyuX" <junyux.jiang@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Jiang, JunyuX" <junyux.jiang@intel.com>
Subject: Re: [dts] [PATCH] test_plans: add test plan enable_jumboframe_for_vf
Date: Wed, 4 Dec 2019 06:51:34 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB7D40B@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20191203015211.3878-1-junyux.jiang@intel.com>
1, this test plan is a part of daemon, please add them into test_plans/vf_daemon_test_plan.rst
2, not only support Niantic, but also support Fortville.
3, be care of your expression, this is a formal document.
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Junyu Jiang
> Sent: Tuesday, December 3, 2019 9:52 AM
> To: dts@dpdk.org
> Cc: Jiang, JunyuX <junyux.jiang@intel.com>
> Subject: [dts] [PATCH] test_plans: add test plan enable_jumboframe_for_vf
>
> Signed-off-by: Junyu Jiang <junyux.jiang@intel.com>
> ---
> .../enable_jumboframe_for_vf_test_plan.rst | 158 ++++++++++++++++++
> 1 file changed, 158 insertions(+)
> create mode 100644 test_plans/enable_jumboframe_for_vf_test_plan.rst
>
> diff --git a/test_plans/enable_jumboframe_for_vf_test_plan.rst
> b/test_plans/enable_jumboframe_for_vf_test_plan.rst
> new file mode 100644
> index 0000000..ff93a93
> --- /dev/null
> +++ b/test_plans/enable_jumboframe_for_vf_test_plan.rst
> @@ -0,0 +1,158 @@
> +.. 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.
> +
> +
> +==================================================
> +VF enable jumbo frame by configuring DPDK PF Tests
> +==================================================
> +
> +Description
> +===========
> +
> +when do MTU set on VF port of ixgbe NIC, jumbo frame mode need enable
> +by host pf, to receive Jumbo Frames with a configurable maximum packet
> +length that is greater than the standard maximum Ethernet frame length
> (1518 bytes).
> +
> +Prerequisites
> +=============
> +
> +1. Hardware:
> + Ethernet Controller 10G X550T 1563
> + Ethernet Connection X552/X557-AT 10GBASE-T 15ad
> +
> +2.Bind PF ports to igb_uio driver::
> +
> + usertools/dpdk-devbind.py --bind=igb_uio 0000:af:00.0
> +
> +3.Create 1 VF device from PF devices,then bind the created VF to igb_uio
> driver::
> +
> + echo 1 > /sys/bus/pci/devices/0000\:af\:00.0/max_vfs
> + usertools/dpdk-devbind.py --bind=igb_uio 0000:af:10.0
> +
> +4.Start testpmd on host::
> +
> + ./x86_64-native-linux-gcc/app/testpmd -c 0xf -n 4 -w af:00.0 --file-
> prefix=PF -- -i
> + testpmd> set verbose 1
> + testpmd> set promisc 0 off
> + testpmd> start
> +
> +5.Start VF testpmd::
> +
> + ./x86_64-native-linux-gcc/app/testpmd -c 0xf -n 4 -w af:10.0 --file-
> prefix=VF -- -i
> + testpmd> set verbose 1
> + testpmd> start
> +
> +Test Case1: Mtu is greater than 1518
> +====================================
> +
> +Set MTU on vf port::
> +
> + testpmd> stop
> + testpmd> port stop 0
> + testpmd> port config mtu 0 2000
> + testpmd> port start 0
> + testpmd> start
> +
> +Send the packet what the length is greater than 1518 less than 2000 to PF
> port::
> +
> + sendp([Ether(dst='B4:96:91:57:78:FC')/IP()/("X" * 1600)],
> +iface="enp175s0f1", count=1)
> +
> +Send the packet what the length is greater than 1518 less than 2000 to VF
> port::
> +
> + sendp([Ether(dst='CE:43:0B:2E:AE:64')/IP()/("X" * 1600)],
> +iface="enp175s0f1", count=1)
> +
> +Check that packets length greater than the standard maximum frame
> +(1518) less than 2000 can received on VF port and PF port.
[Lijuan] Verification is only one sentence , I think the "send packets" can also be summarized to one sentence.
> +
> +Send the packet what the length is greater than 2000 to PF port::
> +
> + sendp([Ether(dst='B4:96:91:57:78:FC')/IP()/("X" * 2100)],
> +iface="enp175s0f1", count=1)
> +
> +Send the packet what the length is greater than 2000 to VF port::
> +
> + sendp([Ether(dst='CE:43:0B:2E:AE:64')/IP()/("X" * 2100)],
> +iface="enp175s0f1", count=1)
> +
> +Check that packets length greater than 2000 can not received on VF port
> and PF port.
[Lijuan] please consider packet size == mtu.
> +
> +Quit VF testpmd, and then restart the VF testpmd::
> +
> + testpmd> quit
> + ./x86_64-native-linux-gcc/app/testpmd -c 0xf -n 4 -w af:10.0 --file-
> prefix=VF -- -i
> + testpmd> set verbose 1
> + testpmd> start
> +
> +Send the packet what the length is greater than 1518 less than 2000 to VF
> port again::
> +
> + sendp([Ether(dst='CE:43:0B:2E:AE:64')/IP()/("X" * 1600)],
> +iface="enp175s0f1", count=1)
> +
> +Check that packets length greater than the standard maximum frame
> +(1518) less than 2000 can received on VF port.
> +
> +Send the pkts what the length is greater than 2000 to VF port again::
[Lijuan] pkts => packets
> +
> + sendp([Ether(dst='CE:43:0B:2E:AE:64')/IP()/("X" * 2100)],
> +iface="enp175s0f1", count=1)
> +
> +Check that packets length greater than 2000 can not received on VF port.
> +
> +Test case2: The maximum mtu(9710)
> +=================================
> +
> +Set MTU on vf port::
> +
> + testpmd> stop
> + testpmd> port stop 0
> + testpmd> port config mtu 0 9710
> + testpmd> port start 0
> + testpmd> start
> +
> +Send the packet what the length is 9710 to PF port::
> +
> + sendp([Ether(dst='B4:96:91:57:78:FC')/IP()/("X" * 9676)],
> +iface="enp175s0f1", count=1)
> +
> +Send the packet what the length is 9710 to VF port::
> +
> + sendp([Ether(dst='CE:43:0B:2E:AE:64')/IP()/("X" * 9676)],
> +iface="enp175s0f1", count=1)
> +
> +Check that packets length is 9710 can received on VF port and PF port.
> +
[Lijuan] what's the purpose of below description?
> +Quit VF testpmd, and then restart the VF testpmd::
> +
> + testpmd> quit
> + ./x86_64-native-linux-gcc/app/testpmd -c 0xf -n 4 -w af:10.0 --file-
> prefix=VF -- -i
> + testpmd> set verbose 1
> + testpmd> start
> +
> +Send the pkts what the length is 9710 to VF port::
> +
> + sendp([Ether(dst='CE:43:0B:2E:AE:64')/IP()/("X" * 9676)],
> +iface="enp175s0f1", count=1)
> +
> +Check that packets length is 9710 can received on VF port.
> --
> 2.17.1
prev parent reply other threads:[~2019-12-04 6:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 1:52 Junyu Jiang
2019-12-04 0:43 ` He, Zhiwei
2019-12-04 6:51 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BB7D40B@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=junyux.jiang@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).