From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 152F94CE4 for ; Wed, 8 Feb 2017 10:31:57 +0100 (CET) Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga102.jf.intel.com with ESMTP; 08 Feb 2017 01:31:56 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,346,1477983600"; d="scan'208";a="63226331" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by fmsmga006.fm.intel.com with ESMTP; 08 Feb 2017 01:31:56 -0800 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.77]) by IRSMSX153.ger.corp.intel.com ([169.254.9.160]) with mapi id 14.03.0248.002; Wed, 8 Feb 2017 09:31:55 +0000 From: "Mrozowicz, SlawomirX" To: "Trahe, Fiona" , "dev@dpdk.org" CC: "De Lara Guarch, Pablo" , "Jain, Deepak K" , "Griffin, John" , "Doherty, Declan" Thread-Topic: [PATCH] doc: add limitations section to cryptoperf guide Thread-Index: AdKBX84FoGDRP6tsRlG8mt7btOkE1gAjjCew Date: Wed, 8 Feb 2017 09:31:55 +0000 Message-ID: <158888A50F43E34AAE179517F56C9745653257@IRSMSX103.ger.corp.intel.com> References: <348A99DA5F5B7549AA880327E580B43589182FE2@IRSMSX101.ger.corp.intel.com> In-Reply-To: <348A99DA5F5B7549AA880327E580B43589182FE2@IRSMSX101.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH] doc: add limitations section to cryptoperf guide 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: Wed, 08 Feb 2017 09:31:58 -0000 >-----Original Message----- >From: Trahe, Fiona >Sent: Tuesday, February 7, 2017 5:33 PM >To: dev@dpdk.org >Cc: De Lara Guarch, Pablo ; Mrozowicz, >SlawomirX ; Jain, Deepak K >; Trahe, Fiona ; Griffin, >John ; Doherty, Declan >Subject: [PATCH] doc: add limitations section to cryptoperf guide > >Add limitations to use of the dpdk-test-crypto-perf tool for hardware >accelerator measurements > >Signed-off-by: Fiona Trahe >--- > doc/guides/tools/cryptoperf.rst | 16 ++++++++++++++++ > 1 files changed, 16 insertions(+), 0 deletions(-) > >diff --git a/doc/guides/tools/cryptoperf.rst b/doc/guides/tools/cryptoperf= .rst >index 6832312..af58e78 100644 >--- a/doc/guides/tools/cryptoperf.rst >+++ b/doc/guides/tools/cryptoperf.rst >@@ -41,6 +41,22 @@ chain mode have to be specified in the command line as >application parameters. These parameters are checked using device >capabilities structure. > >+Limitations: >+------------ >+On hardware devices the cycle-count doesn't always represent the actual >+offload cost. The cycle-count only represents the offload cost when the >+hardware accelerator is not fully loaded, when loaded the cpu cycles >+freed up by the offload are still consumed by the test tool and included = in >the cycle-count. >+These cycles are consumed by retries and inefficient API calls >+enqueuing and dequeuing smaller bursts than specified by the cmdline >+parameter. This results in a larger cycle-count measurement and should >+not be interpreted as an offload cost measurement. >+ >+On hardware devices the throughput measurement is not necessarily the >+maximum possible for the device, e.g. it may be necessary to use >+multiple cores to keep the hardware accelerator fully loaded and so measu= re >maximum throughput. >+ >+ > Compiling the Application > ------------------------- > >-- >1.7.0.7 >>From my point of view this information is ok. S=B3awomir