From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 6CB44F72 for ; Wed, 13 Jan 2016 02:41:37 +0100 (CET) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga102.fm.intel.com with ESMTP; 12 Jan 2016 17:41:37 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,286,1449561600"; d="scan'208";a="28336961" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by fmsmga004.fm.intel.com with ESMTP; 12 Jan 2016 17:41:36 -0800 Received: from fmsmsx157.amr.corp.intel.com (10.18.116.73) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 12 Jan 2016 17:41:36 -0800 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by FMSMSX157.amr.corp.intel.com (10.18.116.73) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 12 Jan 2016 17:41:35 -0800 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.111]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.201]) with mapi id 14.03.0248.002; Wed, 13 Jan 2016 09:41:32 +0800 From: "Xu, HuilongX" To: "Liu, Yong" , "dts@dpdk.org" Thread-Topic: [dts] [PATCH V1 1/3] add vf rss test plan Thread-Index: AQHRTSgjcG0WFgkyIE2fHQai+TSCpJ734MPQgADKa9A= Date: Wed, 13 Jan 2016 01:41:32 +0000 Message-ID: References: <1452595994-16505-1-git-send-email-huilongx.xu@intel.com> <86228AFD5BCD8E4EBFD2B90117B5E81E13AFC765@SHSMSX103.ccr.corp.intel.com> In-Reply-To: <86228AFD5BCD8E4EBFD2B90117B5E81E13AFC765@SHSMSX103.ccr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-cr-hashedpuzzle: OEo= Q98= DE1O D6om ELGn F3Nw HYgF HsHn IkTK J0N1 J8T4 KZeL KqDF LCXW LNue LWwt; 1; ZAB0AHMAQABkAHAAZABrAC4AbwByAGcA; Sosha1_v1; 7; {2F4AF989-8D0B-4FA9-ACF6-A292670B0DDC}; aAB1AGkAbABvAG4AZwB4AC4AeAB1AEAAaQBuAHQAZQBsAC4AYwBvAG0A; Wed, 13 Jan 2016 01:41:30 GMT; UgBFADoAIABbAGQAdABzAF0AIABbAFAAQQBUAEMASAAgAFYAMQAgADEALwAzAF0AIABhAGQAZAAgAHYAZgAgAHIAcwBzACAAdABlAHMAdAAgAHAAbABhAG4A x-cr-puzzleid: {2F4AF989-8D0B-4FA9-ACF6-A292670B0DDC} x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dts] [PATCH V1 1/3] add vf rss test plan X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jan 2016 01:41:38 -0000 > -----Original Message----- > From: Liu, Yong > Sent: Tuesday, January 12, 2016 9:34 PM > To: Xu, HuilongX; dts@dpdk.org > Subject: RE: [dts] [PATCH V1 1/3] add vf rss test plan >=20 > Huilong, one question about VF supported hash algorithm. >=20 > > -----Original Message----- > > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of xu,huilong > > Sent: Tuesday, January 12, 2016 6:53 PM > > To: dts@dpdk.org > > Subject: [dts] [PATCH V1 1/3] add vf rss test plan > > > > Signed-off-by: xu,huilong > > --- > > test_plans/vf_rss_test_plan.rst | 182 > > ++++++++++++++++++++++++++++++++++++++++ > > 1 file changed, 182 insertions(+) > > create mode 100644 test_plans/vf_rss_test_plan.rst > > > > diff --git a/test_plans/vf_rss_test_plan.rst > > b/test_plans/vf_rss_test_plan.rst > > new file mode 100644 > > index 0000000..f832924 > > --- /dev/null > > +++ b/test_plans/vf_rss_test_plan.rst > > @@ -0,0 +1,182 @@ > > +.. Copyright (c) <2016>, 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. > > + > > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > +Fortville RSS full support - Support configuring hash functions > > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > + > > +This document provides test plan for testing the function of Fortville= : > > +Support configuring hash functions. > > + > > +Prerequisites > > +------------- > > + > > +2x Intel? 82599 (Niantic) NICs (2x 10GbE full duplex optical ports per > > NIC) > > +1x Fortville_eagle NIC (4x 10G) > > +1x Fortville_spirit NIC (2x 40G) > > +2x Fortville_spirit_single NIC (1x 40G) > > + > > +The one port of the 82599 connect to the Fortville_eagle; > > +The one port of Fortville_spirit connect to Fortville_spirit_single. > > +The three kinds of NICs are the target NICs. the connected NICs can > send > > packets > > +to these three NICs using scapy. > > + > > +Network Traffic > > +--------------- > > + > > +The RSS feature is designed to improve networking performance by load > > balancing > > +the packets received from a NIC port to multiple NIC RX queues, with > each > > queue > > +handled by a different logical core. > > + > > +#1. The receive packet is parsed into the header fields used by the > hash > > +operation (such as IP addresses, TCP port, etc.) > > + > > +#2. A hash calculation is performed. The Fortville supports four hash > > function: > > +Toeplitz, simple XOR and their Symmetric RSS. > > + >=20 > Here mentioned that Fortville support three different types of algorithm. > But in following plan, only default algorithm is validated. > My question is that whether VF can't change algorithm or here just tope? >=20 FVL VF want change hash algorithm, host driver must is dpdk driver, because= VF hash algorithm config is a global config. In this plan, only used kernel driver. I will add new case for dpdk host dr= iver. > > +#3. The seven LSBs of the hash result are used as an index into a > 128/512 > > entry > > +'redirection table'. > > + > > +The RSS RETA update feature is designed to make RSS more flexible by > > allowing > > +users to define the correspondence between the seven LSBs of hash > result > > and > > +the queue id(RSS output index) by themself. > > + > > + > > +Test Case: test_rss_hash > > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > + > > +The following RX Ports/Queues configurations have to be benchmarked: > > + > > +- 1 RX port / 4 RX queues (1P/4Q) > > + > > + > > +Testpmd configuration - 4 RX/TX queues per port > > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > + > > +:: > > + > > + testpmd -c 1f -n 3 -- -i --rxq=3D4 --txq=3D4 > > + > > +Testpmd Configuration Options > > +----------------------------- > > + > > +By default, a single logical core runs the test. > > +The CPU IDs and the number of logical cores running the test in > parallel > > can > > +be manually set with the ``set corelist X,Y`` and the ``set nbcore N`` > > +interactive commands of the ``testpmd`` application. > > +#1. got the pci device id of DUT, for example, > > + > > +./dpdk_nic_bind.py --st > > + > > +0000:81:00.0 'Ethernet Controller X710 for 10GbE SFP+' if=3Dens259f0 > > drv=3Di40e unused=3D > > +0000:81:00.1 'Ethernet Controller X710 for 10GbE SFP+' if=3Dens259f1 > > drv=3Di40e unused=3D > > + > > +#2. create 2 VFs from 2 PFs, > > + > > +echo 1 > /sys/bus/pci/devices/0000\:81\:00.0/sriov_numvfs > > +echo 1 > /sys/bus/pci/devices/0000\:81\:00.1/sriov_numvfs > > +./dpdk_nic_bind.py --st > > + > > +0000:81:00.0 'Ethernet Controller X710 for 10GbE SFP+' if=3Dens259f0 > > drv=3Di40e unused=3D > > +0000:81:00.1 'Ethernet Controller X710 for 10GbE SFP+' if=3Dens259f1 > > drv=3Di40e unused=3D > > +0000:81:02.0 'XL710/X710 Virtual Function' unused=3D > > +0000:81:0a.0 'XL710/X710 Virtual Function' unused=3D > > + > > +#3. detach VFs from the host, bind them to pci-stub driver, > > + > > +/sbin/modprobe pci-stub > > + > > +using `lspci -nn|grep -i ethernet` got VF device id, for example "8086 > > 154c", > > + > > +echo "8086 154c" > /sys/bus/pci/drivers/pci-stub/new_id > > +echo 0000:81:02.0 > /sys/bus/pci/devices/0000:08:02.0/driver/unbind > > +echo 0000:81:02.0 > /sys/bus/pci/drivers/pci-stub/bind > > + > > +echo "8086 154c" > /sys/bus/pci/drivers/pci-stub/new_id > > +echo 0000:81:0a.0 > /sys/bus/pci/devices/0000:08:0a.0/driver/unbind > > +echo 0000:81:0a.0 > /sys/bus/pci/drivers/pci-stub/bind > > + > > + or using the following more easy way, > > + > > + virsh nodedev-detach pci_0000_81_02_0; > > + virsh nodedev-detach pci_0000_81_0a_0; > > + > > + ./dpdk_nic_bind.py --st > > + > > + 0000:81:00.0 'Ethernet Controller X710 for 10GbE SFP+' if=3Dens259f0 > > drv=3Di40e unused=3D > > + 0000:81:00.1 'Ethernet Controller X710 for 10GbE SFP+' if=3Dens259f1 > > drv=3Di40e unused=3D > > + 0000:81:02.0 'XL710/X710 Virtual Function' if=3D drv=3Dpci-stub unus= ed=3D > > + 0000:81:0a.0 'XL710/X710 Virtual Function' if=3D drv=3Dpci-stub unus= ed=3D > > + > > + it can be seen that VFs 81:02.0 & 81:0a.0 's drv is pci-stub. > > + > > +#4. passthrough VFs 81:02.0 & 81:0a.0 to vm0, and start vm0, > > + > > + /usr/bin/qemu-system-x86_64 -name vm0 -enable-kvm \ > > + -cpu host -smp 4 -m 2048 -drive file=3D/home/image/sriov-fc20-1.img = - > > vnc :1 \ > > + -device pci-assign,host=3D81:02.0,id=3Dpt_0 \ > > + -device pci-assign,host=3D81:0a.0,id=3Dpt_1 > > + > > +#5. login vm0, got VFs pci device id in vm0, assume they are 00:06.0 & > > 00:07.0, bind them to igb_uio driver, > > +and then start testpmd, set it in mac forward mode, > > + > > +./tools/dpdk_nic_bind.py --bind=3Digb_uio 00:06.0 00:07.0 > > + > > +#6. Reta Configuration. 128 reta entries configuration:: > > + > > + testpmd command: port config 0 rss reta (hash_index,queue_id) > > + > > +#7. PMD fwd only receive the packets:: > > + > > + testpmd command: set fwd rxonly > > + > > +#8. rss recived package type configuration two received packet types > > configuration:: > > + > > + testpmd command: port config 0 rss ip/udp/tcp > > + > > +#9. verbose configuration:: > > + > > + testpmd command: set verbose 8 > > + > > +#10. start packet receive:: > > + > > + testpmd command: start > > +#11. send packet and check rx port received packet by different queue. > > + different hash type send different packet, example hash type is ip, > > packet src and dts ip not different > > + sendp([Ether(dst=3D"90:e2:ba:36:99:3c")/IP(src=3D"192.168.0.4", > > dst=3D"192.168.0.5")], iface=3D"eth3") > > + sendp([Ether(dst=3D"90:e2:ba:36:99:3c")/IP(src=3D"192.168.0.5", > > dst=3D"192.168.0.4")], iface=3D"eth3") > > +Test Case: test_reta > > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > + this case test hash reta table, the test steps same with > test_rss_hash > > except config hash reta table > > +#1 before send packet, config hash reta,512(niantic nic have 128 reta) > > reta entries configuration:: > > + > > + testpmd command: port config 0 rss reta (hash_index,queue_id) > > -- > > 1.9.3