From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id A45301B3B4 for ; Thu, 31 Jan 2019 03:07:46 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Jan 2019 18:07:45 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,542,1539673200"; d="scan'208";a="316326512" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by fmsmga005.fm.intel.com with ESMTP; 30 Jan 2019 18:07:45 -0800 Received: from fmsmsx161.amr.corp.intel.com (10.18.125.9) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 30 Jan 2019 18:07:45 -0800 Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by FMSMSX161.amr.corp.intel.com (10.18.125.9) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 30 Jan 2019 18:07:45 -0800 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.110]) by SHSMSX103.ccr.corp.intel.com ([169.254.4.194]) with mapi id 14.03.0415.000; Thu, 31 Jan 2019 10:07:43 +0800 From: "Tu, Lijuan" To: "Peng, Yuan" , "dts@dpdk.org" CC: "Peng, Yuan" Thread-Topic: [dts] [PATCH]test_plans: discard ip_pipeline_test_plan.rst Thread-Index: AQHUtroD0QSsebjFlUufyZqFT90U+aXIpgJw Date: Thu, 31 Jan 2019 02:07:42 +0000 Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA1F28C@SHSMSX101.ccr.corp.intel.com> References: <1548646515-38819-1-git-send-email-yuan.peng@intel.com> In-Reply-To: <1548646515-38819-1-git-send-email-yuan.peng@intel.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMzIxOTEzOTktODQ4OC00ZDU1LWEwYzctMWRmZDRiNGMyMWYzIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiYWN5eEZvNStoclZjZ3hRSnRGN1UxKzhaZkxUS1h5Qmt5dmZ2UDVrQ09sekNiSHJ0SGs5bnRFbldqdklzbEdiSyJ9 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]test_plans: discard ip_pipeline_test_plan.rst 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: Thu, 31 Jan 2019 02:07:47 -0000 Applied, thanks > -----Original Message----- > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Peng Yuan > Sent: Monday, January 28, 2019 11:35 AM > To: dts@dpdk.org > Cc: Peng, Yuan > Subject: [dts] [PATCH]test_plans: discard ip_pipeline_test_plan.rst >=20 > Discard the old ip_pipeline_test_plan.rst, and will submit a new test pla= n for > ip_pipeline sample. >=20 > Signed-off-by: Peng Yuan >=20 > diff --git a/test_plans/ip_pipeline_test_plan.rst > b/test_plans/ip_pipeline_test_plan.rst > deleted file mode 100644 > index 72c25cf..0000000 > --- a/test_plans/ip_pipeline_test_plan.rst > +++ /dev/null > @@ -1,319 +0,0 @@ > -.. Copyright (c) <2010-2017>, 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 > -IP Pipeline Application Tests > -=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 ``ip_pipeline application`` is the main DPDK Packet Framework (PFW) = - > application. > - > -The application allows setting of a pipeline through the PFW. Currently = the - > application set a pipeline using 2 main features, routing and flow contro= l -and, in > addition, ARP is used. > - > -The application has an interactive session when started to allow in-app = - > configuration. > - > -This application uses 5 CPU cores, reception, flow control, routing and = - > transmission. > - > -The traffic will pass through the pipeline if meets the following condit= ions: > - > -- If ``flow add all`` is used in the setup then: > - > - - TCP/IPv4 > - - IP destination =3D A.B.C.D with A =3D 0 and B,C,D random > - - IP source =3D 0.0.0.0 > - - TCP destination port =3D 0 > - - TCP source port =3D 0 > - > -- If ``flow add all`` is not used then there is no restrictions. > - > -Prerequisites > -=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > - > -Launch the ``ip_pipeline`` app with 5 lcores and two ports:: > - > - $ examples/ip_pipeline/build/ip_pipeline -c 0x3e -n = -- -p > - > - > -The expected prompt is:: > - > - pipeline> > - > - > -The selected ports will be called 0 and 1 in the following instructions. > - > -Tcpdump is used in test as a traffic sniffer unless otherwise stated. Tc= pdump -is > set in both ports to check that traffic is sent and forwarded, or not -fo= rwarded. > - > -Scapy is used in test as traffic generator unless otherwise stated. > - > -The PCAP driver is used in some tests as a traffic generator and sniffer= . > - > -NOTE: ``ip_pipeline`` is currently hardcoded to start the reception from= ports - > automatically. Prior to running the test described in this document this = -behavior > has to be modified by commenting out the following lines in > -``examples/ip_pipeline/pipeline_rx.c``:: > - > - /* Enable input ports */ > - for (i =3D 0; i < app.n_ports; i ++) { > - if (rte_pipeline_port_in_enable(p, port_in_id[i])) { > - rte_panic("Unable to enable input port %u\n", port_i= n_id[i]); > - } > - } > - > - > -Test Case: test_incremental_ip > -=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 > - > -Create a PCAP file containing permutations of the following parameters: > - > - - TCP/IPv4. > - - 64B size. > - - Number of frames sent. 1, 3, 63, 64, 65, 127, 128. > - - Interval between frames. 0s, 0.7s. > - - Incremental destination IP address. 1 by 1 increment on every frame. > - - Maximum IP address 255.128.0.0. > - > -Start the ``ip_pipeline`` application as described in prerequisites. Run= the - > default config script:: > - > - pipeline> run examples/ip_pipeline/ip_pipeline.sh > - > -Start port reception:: > - > - link 0 up link 1 up > - > -Send the generated PCAP file from port 1 to 0, check that all frames are= - > forwarded to port 0. Send the generated PCAP file from port 0 to 1, check= that - > all frames are forwarded to port 0. > - > -Stop port reception:: > - > - link 0 down link 1 down > - > -Test Case: test_frame_sizes > -=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 > - > -Create a PCAP file containing permutations of the following parameters: > - > - - TCP/IPv4. > - - Frame size 64, 65, 128. > - - 100 frames. > - - 0.5s interval between frames. > - - Incremental destination IP address. 1 by 1 increment on every frame. > - - Maximum IP address 255.128.0.0. > - > -Start the ``ip_pipeline`` application as described in prerequisites. Run= the - > default config script:: > - > - pipeline> run examples/ip_pipeline/ip_pipeline.sh > - > -Start port reception:: > - > - link 0 up link 1 up > - > -Send the generated PCAP file from port 1 to 0, check that all frames are= - > forwarded to port 0. Send the generated PCAP file from port 0 to 1, check= that - > all frames are forwarded to port 0. > - > -Stop port reception:: > - > - link 0 down link 1 down > - > -Test Case: test_pcap_incremental_ip > -=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 > - > -Compile the DPDK to use the PCAP driver. Modify the target config file t= o allow > -PCAP driver:: > - > - sed -i > 's/CONFIG_RTE_LIBRTE_PMD_PCAP=3Dn$/CONFIG_RTE_LIBRTE_PMD_PCAP=3Dy/' > config/defconfig_ > - > -Create a PCAP file containing permutations of the following parameters: > - > - - TCP/IPv4. > - - 64B size. > - - Number of frames sent. 1, 3, 63, 64, 65, 127, 128. > - - Incremental destination IP address. 1 by 1 increment on every frame. > - - Maximum IP address 255.128.0.0. > - > -Start the ``ip_pipeline`` application using pcap devices:: > - > - $ ./examples/ip_pipeline/build/ip_pipeline -c -n > --use-device -- -p 0x3 > - > - : 'eth_pcap0;rx_pcap=3D/root/ 0>;tx_pcap=3D/tmp/port0out.pcap,eth_pcap1;rx_pcap=3D/root/ 1>;tx_pcap=3D/tmp/port1out.pcap' > - > -Run the default config script:: > - > - pipeline> run examples/ip_pipeline/ip_pipeline.sh > - > -As the traffic is sent and received by PCAP devices the traffic flow is = -triggered > by enabling the ports:: > - > - link 0 up link 1 up > - > -Wait 1s to allow all frames to be sent and stop the ports:: > - > - link 0 down link 1 down > - > -Check the results PCAP files ``tmp/port0out.pcap`` and ``tmp/port1out.pc= ap``, - > the frames must be received in port 0, ``tmp/port0out.pcap``. > - > -Test Case: test_pcap_frame_sizes > -=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 > - > -Compile DPDK to use PCAP driver. Modify the target config file to allow = PCAP > -driver:: > - > - sed -i > 's/CONFIG_RTE_LIBRTE_PMD_PCAP=3Dn$/CONFIG_RTE_LIBRTE_PMD_PCAP=3Dy/' > - config/defconfig_ > - > -Create a PCAP file containing permutations of the following parameters: > - > - - TCP/IPv4. > - - Frame sizes 64, 65, 128. > - - Number of frames sent. 1, 3, 63, 64, 65, 127, 128. > - - Incremental destination IP address. 1 by 1 increment on every frame. > - - Maximum IP address 255.128.0.0. > - > -Start the ``ip_pipeline`` application using pcap devices:: > - > - $ ./examples/ip_pipeline/build/ip_pipeline -c -n > --use-device -- -p 0x3 > - > - : 'eth_pcap0;rx_pcap=3D/root/ 0>;tx_pcap=3D/tmp/port0out.pcap,eth_pcap1;rx_pcap=3D/root/ 1>;tx_pcap=3D/tmp/port1out.pcap' > - > -Run the default config script:: > - > - pipeline> run examples/ip_pipeline/ip_pipeline.sh > - > -As the traffic is sent and received by PCAP devices the traffic flow is = -triggered > by enabling the ports:: > - > - link 0 up > - link 1 up > - > -Wait 1s to allow all frames to be sent and stop the ports:: > - > - link 0 down > - link 1 down > - > - > -Check the results PCAP files ``tmp/port0out.pcap`` and ``tmp/port1out.pc= ap``, - > the frames must be received in port 0, ``tmp/port0out.pcap``. > - > -Test Case: test_flow_management > -=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 test checks the flow addition and removal feature in the packet fra= mework. > - > -Create a PCAP file containing the following traffic: > - > - - TCP/IPv4. > - - Frame size 64. > - - Source IP address 0.0.0.0 > - - Destination IP addresses: '0.0.0.0', '0.0.0.1', '0.0.0.127', '0.0.0.1= 28', > - '0.0.0.255', '0.0.1.0', '0.0.127.0', '0.0.128.0', '0.0.129.0', '0.0.2= 55.0', > - '0.127.0.0', '0.127.1.0', '0.127.127.0', '0.127.255.0', '0.127.255.25= 5' > - > -Start the ``ip_pipeline`` application as described in prerequisites and = set up -the > following configuration:: > - > - pipeline> arp add 0 0.0.0.1 0a:0b:0c:0d:0e:0f > - pipeline> arp add 1 0.128.0.1 1a:1b:1c:1d:1e:1f > - pipeline> route add 0.0.0.0 9 0 0.0.0.1 > - pipeline> route add 0.128.0.0 9 1 0.128.0.1 > - > -Start port reception:: > - > - link 0 up link 1 up > - > -1. Send the pcap file and check that the number of frames forwarded matc= hes > the > - number of flows added (starting at 0) > - > -2. Add a new flow matching one of the IP address:: > - > - pipeline> flow add 0.0.0.0 0 0 0 > - > -3. Repeat Step 1 until all the frames pass > - > -4. Remove a flow previously added:: > - > - pipeline> flow del 0.0.0.0 0 0 0 > - > -5. Check if a frames less is forwarded. > - > -6. Repeat from step 4 until no frames are forwarded. > - > -Test Case: test_route_management > -=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 test checks the route addition and removal feature in the packet > framework. > - > -Create a PCAP file containing the following traffic: > - > - - TCP/IPv4. > - - Frame size 64. > - - Source IP address 0.0.0.0 > - - Destination IP addresses: '0.0.0.0', '0.0.0.1', '0.0.0.127', '0.0.0.1= 28', > - '0.0.0.255', '0.0.1.0', '0.0.127.0', '0.0.128.0', '0.0.129.0', '0.0.2= 55.0', > - '0.127.0.0', '0.127.1.0', '0.127.127.0', '0.127.255.0', '0.127.255.25= 5' > - > -Start the ``ip_pipeline`` application as described in prerequisites and = set up -the > following configuration:: > - > - pipeline> arp add 0 0.0.0.1 0a:0b:0c:0d:0e:0f > - pipeline> arp add 1 0.128.0.1 1a:1b:1c:1d:1e:1f > - pipeline> flow add all > - > -Start port reception:: > - > - link 0 up link 1 up > - > -1. Send the pcap file and check that the number of frames forwarded matc= hes > - the number of routes added (starting at 0) > - > -2. Add a new route matching one of the IP address:: > - > - pipeline> route add 32 0.0.0.1 > - > -3. Repeat Step 1 until all the frames pass > - > -4. Remove a route previously added:: > - > - pipeline> route del 32 > - > -5. Check if a frames less is forwarded. > - > -6. Repeat from step 4 until no frames are forwarded. > -- > 2.5.0