From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 91227A0096 for ; Thu, 11 Apr 2019 08:54:34 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 2B44D5F16; Thu, 11 Apr 2019 08:54:34 +0200 (CEST) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 58CB05F13 for ; Thu, 11 Apr 2019 08:54:32 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Apr 2019 23:54:30 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,336,1549958400"; d="scan'208";a="160668516" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by fmsmga004.fm.intel.com with ESMTP; 10 Apr 2019 23:54:30 -0700 Received: from fmsmsx125.amr.corp.intel.com (10.18.125.40) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 10 Apr 2019 23:54:29 -0700 Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by FMSMSX125.amr.corp.intel.com (10.18.125.40) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 10 Apr 2019 23:54:29 -0700 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.206]) by SHSMSX103.ccr.corp.intel.com ([169.254.4.93]) with mapi id 14.03.0415.000; Thu, 11 Apr 2019 14:54:27 +0800 From: "Xu, Qian Q" To: "Wan, Zhe" , "Tu, Lijuan" , "dts@dpdk.org" Thread-Topic: [dts] [PATCH V1] test_plans/scatter: test plan revise Thread-Index: AQHU5gsUvGMH8vsG/E+9KoKyTpbtCqYqM3iAgAvcrICAAIpSkA== Date: Thu, 11 Apr 2019 06:54:25 +0000 Message-ID: <82F45D86ADE5454A95A89742C8D1410E40411014@shsmsx102.ccr.corp.intel.com> References: <1553877003-190139-1-git-send-email-zhe.wan@intel.com> <8CE3E05A3F976642AAB0F4675D0AD20E0BA5B7F3@SHSMSX101.ccr.corp.intel.com> <861C16A15685B44AA870C0D2A97B60458978FE5A@SHSMSX101.ccr.corp.intel.com> In-Reply-To: <861C16A15685B44AA870C0D2A97B60458978FE5A@SHSMSX101.ccr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNmRiNzg2NWUtNmFiZi00MGRlLWI3OTYtN2ZlMTgxOTVkNDhmIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiUnhMc1VERURPcVl6OTZPSHlzUFlZY1NxUmxhY3NrUUF0R2w0TnhmT3Mxc3FpSzMyOTJBXC8zMWVjdHkwQlwvY1c1In0= x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.600.7 dlp-reaction: no-action 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] test_plans/scatter: test plan revise 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: , Errors-To: dts-bounces@dpdk.org Sender: "dts" Zhe, you may set some MACRO here instead of the absolute number.=20 > -----Original Message----- > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Wan, Zhe > Sent: Thursday, April 11, 2019 2:38 PM > To: Tu, Lijuan ; dts@dpdk.org > Subject: Re: [dts] [PATCH V1] test_plans/scatter: test plan revise >=20 > Hi Lijuan, > About the addition of '--tx-offloads=3D0x00008000', the background is DPD= K-5618 > (https://jira.devtools.intel.com/browse/DPDK-5618). > The test plan didn't updated accordingly. >=20 > commit 3743153fac89b821959fbb882058bf81177b07e7. > Author: xu,gang > Date: Tue Jul 10 10:49:58 2018 +0800 >=20 > tests/scatter: fix selected wrong vector path on ixgbe >=20 > When no tx offload enabled, ixgbe will chose vector path which can no= t > support scatter. After enabling DEV_TX_OFFLOAD_MULTI_SEGS options, ca= n > avoid this problem. >=20 > Signed-off-by: xu,gang >=20 > https://mails.dpdk.org/archives/dts/2018-July/004208.html >=20 > This TX offload capability defined in DPDK code > 'dpdk/lib/librte_ethdev/rte_ethdev.h' > #define DEV_TX_OFFLOAD_MULTI_SEGS 0x00008000 /**< Device supports > multi segment send. */ >=20 >=20 > Thanks! > BR, > Wan,Zhe >=20 > -----Original Message----- > From: Tu, Lijuan > Sent: Thursday, April 04, 2019 1:30 AM > To: Wan, Zhe ; dts@dpdk.org > Cc: Wan, Zhe > Subject: RE: [dts] [PATCH V1] test_plans/scatter: test plan revise >=20 > Hi zhe, >=20 > Could you please kindly add some interpretation about why is --tx- > offloads=3D0x00008000 ? >=20 > thanks >=20 > > -----Original Message----- > > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Zhe > > Sent: Friday, March 29, 2019 9:30 AM > > To: dts@dpdk.org > > Cc: Wan, Zhe > > Subject: [dts] [PATCH V1] test_plans/scatter: test plan revise > > > > From: Zhe Wan > > > > Signed-off-by: Zhe Wan > > --- > > test_plans/scatter_test_plan.rst | 27 ++++++++++++--------------- > > 1 file changed, 12 insertions(+), 15 deletions(-) > > > > diff --git a/test_plans/scatter_test_plan.rst > > b/test_plans/scatter_test_plan.rst > > index cf5e1e5..ed1aaaa 100644 > > --- a/test_plans/scatter_test_plan.rst > > +++ b/test_plans/scatter_test_plan.rst > > @@ -72,15 +72,15 @@ the CRC from the packet before returning it. > > As a whole, the following packet lengths (CRC included) must be > > tested to check all packet memory configurations: > > > > -#. packet length < mbuf data buffer size > > +1) packet length < mbuf data buffer size > > > > -#. packet length =3D mbuf data buffer size > > +2) packet length =3D mbuf data buffer size > > > > -#. packet length =3D mbuf data buffer size + 1 > > +3) packet length =3D mbuf data buffer size + 1 > > > > -#. packet length =3D mbuf data buffer size + 4 > > +4) packet length =3D mbuf data buffer size + 4 > > > > -#. packet length =3D mbuf data buffer size + 5 > > +5) packet length =3D mbuf data buffer size + 5 > > > > In cases 1) and 2), the hardware RX engine stores the packet data and > > the CRC in a single buffer. > > @@ -101,21 +101,18 @@ Assuming that ports ``0`` and ``1`` of the test > > target are directly connected to a Traffic Generator, launch the > > ``testpmd`` application with the following > > arguments:: > > > > - ./build/app/testpmd -cffffff -n 3 -- -i --rxd=3D1024 --txd=3D1024 \ > > - --burst=3D144 --txpt=3D32 --txht=3D8 --txwt=3D8 --txfreet=3D0 --rxfr= eet=3D64 \ > > - --mbcache=3D200 --portmask=3D0x3 --mbuf-size=3D1024 > > + ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x6 -n 4 \ > > + -- -i --mbcache=3D200 --mbuf-size=3D2048 --portmask=3D0x1 \ > > + --max-pkt-len=3D9000 --port-topology=3Dloop --tx-offloads=3D0x000080= 00 > > > > The -n command is used to select the number of memory channels. It > > should match the number of memory channels on that setup. > > > > -Setting the size of the mbuf data buffer to 1024 makes 1025-bytes > > input packets -(CRC included) and larger packets to be stored in two > > buffers by the hardware -RX engine. > > - > > -Test Case: Mbuf 1024 traffic > > +Test Case: Scatter Mbuf 2048 > > =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 > > > > Start packet forwarding in the ``testpmd`` application with the > > ``start`` command. > > -Send 5 packets of lengths (CRC included) 1023, 1024, 1025, 1028, and 1= 029. > > +Send 5 packets,the lengths are mbuf-size + offset (CRC included). > > +The offset are -1, 0, 1, 4, 5 respectively. > > Check that the same amount of frames and bytes are received back by > > the Traffic -Generator from its port connected to the target's port 1. > > +Generator from it's port connected to the target's port 1. > > -- > > 1.8.3.1