From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 525F01B5A3 for ; Fri, 23 Nov 2018 16:00:05 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Nov 2018 07:00:04 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,270,1539673200"; d="scan'208";a="93438364" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by orsmga006.jf.intel.com with ESMTP; 23 Nov 2018 07:00:03 -0800 Received: from fmsmsx116.amr.corp.intel.com (10.18.116.20) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 23 Nov 2018 07:00:03 -0800 Received: from hasmsx107.ger.corp.intel.com (10.184.198.27) by fmsmsx116.amr.corp.intel.com (10.18.116.20) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 23 Nov 2018 07:00:03 -0800 Received: from hasmsx112.ger.corp.intel.com ([169.254.11.97]) by hasmsx107.ger.corp.intel.com ([169.254.2.159]) with mapi id 14.03.0415.000; Fri, 23 Nov 2018 17:00:00 +0200 From: "Jozwiak, TomaszX" To: "Varghese, Vipin" , "dev@dpdk.org" , "Trahe, Fiona" , "Shally.Verma@cavium.com" , "akhil.goyal@nxp.com" Thread-Topic: [dpdk-dev] [PATCH v3 3/5] doc/guides/tools: add doc files Thread-Index: AQHUgy1tHipOGRSCFEC8llwmJU2OoaVdUHoAgAAigKA= Date: Fri, 23 Nov 2018 14:59:59 +0000 Message-ID: References: <1541151842-8746-1-git-send-email-tomaszx.jozwiak@intel.com> <1542978409-28668-1-git-send-email-tomaszx.jozwiak@intel.com> <1542978409-28668-4-git-send-email-tomaszx.jozwiak@intel.com> <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D2C1ADF@BGSMSX101.gar.corp.intel.com> In-Reply-To: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D2C1ADF@BGSMSX101.gar.corp.intel.com> Accept-Language: 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-originating-ip: [10.103.104.46] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v3 3/5] doc/guides/tools: add doc files X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2018 15:00:05 -0000 > -----Original Message----- > From: Varghese, Vipin > Sent: Friday, November 23, 2018 3:53 PM > To: Jozwiak, TomaszX ; dev@dpdk.org; Trahe, > Fiona ; Jozwiak, TomaszX > ; Shally.Verma@cavium.com; > akhil.goyal@nxp.com > Subject: RE: [dpdk-dev] [PATCH v3 3/5] doc/guides/tools: add doc files >=20 > Hi Tomasz, >=20 > >=20 > > +dpdk-test-compress-perf Application > > +=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 > > + >=20 > Suggestion to remove extra '=3D' True , Thx >=20 > > +The ``dpdk-test-compress-perf`` tool is a Data Plane Development Kit > > +(DPDK) utility that allows measuring performance parameters of PMDs >=20 > Is this test application or utility like procinfo or pdump? 'tool application' will change this. >=20 > > +available in the compress tree. The application reads the data from a > > +file (--input-file), dumps all the file into a buffer and fills out > > +the data of input mbufs, which are passed to compress device with > > +compression > > operations. > > +Then, the output buffers are fed into the decompression stage, and > > +the resulting data is compared against the original data > > +(verification phase). After that, a number of iterations are > > +performed, compressing first and decompressing later, to check the > > +throughput rate (showing cycles/iteration, cycles/Byte and Gbps, for > compression and decompression). > > + > > + > > +Limitations > > +~~~~~~~~~~~ > > + >=20 > Suggestion to remove extra '~' True, will do >=20 > > +* Only supports the fixed compression and stateless operation. > > + >=20 > Is the limitation of the application that it will not cover stateful? In that initial version yes. Will be updated in future versions. >=20 > > +Command line options > > +-------------------- > > + > > + ``--driver-name NAME``: compress driver to use > > + > > + ``--input-file NAME``: file to compress and decompress > > + > > + ``--extended-input-sz N``: extend file data up to this size (default: > > + no extension) > > + > > + ``--seg-sz N``: size of segment to store the data (default: 2048) > > + > > + ``--burst-sz N``: compress operation burst size > > + > > + ``--pool-sz N``: mempool size for compress operations/mbufs (default: > > + 8192) > > + > > + ``--max-num-sgl-segs N``: maximum number of segments for each mbuf > > + (default: 16) > > + > > + ``--num-iter N``: number of times the file will be > > + compressed/decompressed (default: 10000) > > + > > + ``--operation [comp/decomp/comp_and_decomp]``: perform test on > > + compression, decompression or both operations > > + > > + ``--huffman-enc [fixed/default]``: Huffman encoding (default: fixed) > > + > > + ``--compress-level N``: compression level, which could be a single > > + value, list or range (default: range between 1 and 9) > > + > > + ``--window-sz N``: base two log value of compression window size > > + (default: max supported by PMD) > > + > > + ``-h``: prints this help > > + > > + > > +Compiling the Application > > +------------------------- > > + > > +**Step 1: PMD setting** > > + > > +The ``dpdk-test-compress-perf`` tool depends on compression device > > +drivers PMD which can be disabled by default in the build > > +configuration file > > ``common_base``. > > +The compression device drivers PMD which should be tested can be > > +enabled > > by setting:: > > + > > + CONFIG_RTE_LIBRTE_PMD_ISAL=3Dy > > + >=20 > Does this application only run with ISAL? If yes will it be ok to mention= this in > limitation? No, should be eg.: Will update this >=20 > > + > > +Running the Application > > +----------------------- > > + > > +The tool application has a number of command line options. Here is > > +the > > sample command line: > > + >=20 > Here we are using 'tool application'. Would either one of application or = utility > state the right usage? True, will update this, Thx -- Tomek