Message ID | 20210114104125.2890107-1-ciara.power@intel.com (mailing list archive) |
---|---|
Headers |
Return-Path: <dev-bounces@dpdk.org> X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id DB31FA0A02; Thu, 14 Jan 2021 11:41:38 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DA557141107; Thu, 14 Jan 2021 11:41:33 +0100 (CET) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by mails.dpdk.org (Postfix) with ESMTP id A8C4D141100 for <dev@dpdk.org>; Thu, 14 Jan 2021 11:41:32 +0100 (CET) IronPort-SDR: oSPp+O+q/q1nMeTGPvckyCB9h7LwMhA7J0CDNtM338xjb0rj6E2Q4NSkWdOjIl47CUNndiWxbF pforRGFG3DYQ== X-IronPort-AV: E=McAfee;i="6000,8403,9863"; a="196995872" X-IronPort-AV: E=Sophos;i="5.79,347,1602572400"; d="scan'208";a="196995872" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Jan 2021 02:41:31 -0800 IronPort-SDR: lWdgw9tfooQnQNLaZtLXyxQoGlikRXtTh66H5w9/nzPFXnLvCGyBgL5G9TBZZ/xlZaM0+7KvcA HLiouLgcRgAQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.79,347,1602572400"; d="scan'208";a="382223602" Received: from silpixa00400355.ir.intel.com (HELO silpixa00400355.ger.corp.intel.com) ([10.237.223.148]) by orsmga008.jf.intel.com with ESMTP; 14 Jan 2021 02:41:29 -0800 From: Ciara Power <ciara.power@intel.com> To: dev@dpdk.org Cc: declan.doherty@intel.com, akhil.goyal@nxp.com, stephen@networkplumber.org, adamx.dybkowski@intel.com, Ciara Power <ciara.power@intel.com> Date: Thu, 14 Jan 2021 10:41:21 +0000 Message-Id: <20210114104125.2890107-1-ciara.power@intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20201211173114.1924772-1-ciara.power@intel.com> References: <20201211173114.1924772-1-ciara.power@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-dev] [PATCH v2 0/4] add crypto perf test graphing script X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> |
Series | add crypto perf test graphing script | |
Message
Power, Ciara
Jan. 14, 2021, 10:41 a.m. UTC
This patchset introduces a python script to run various crypto performance test cases, and graph the results in a consumable manner. The test suites are configured via JSON file. Some config files are provided, or the user may create one. Currently throughput and latency ptests for devices crypto_qat, crypto_aesni_mb and crypto_aesni_gcm are supported. The final collection of graphs are output in PDF format, with multiple PDFs per test suite, one for each graph type. Some fixes are included for the throughput performance test and latency performance test csv outputs also. v2: - Reduced changes to only fix csv format for all perf test types. - Added functionality for additional args such as config file, output directory and verbose. - Improved help text for script. - Improved script console output. - Added support for latency test cases with burst or buffer size lists. - Split config file into smaller config files, one for each device. - Split output PDFs into smaller files, based on test suite graph types. - Modified output directory naming and structure. - Made some general improvements to script. - Updated and improved documentation. Ciara Power (4): test/cryptodev: fix latency test csv output test/cryptodev: fix csv output format usertools: add script to graph crypto perf results maintainers: update crypto perf app maintainers MAINTAINERS | 3 + app/test-crypto-perf/cperf_test_latency.c | 4 +- .../cperf_test_pmd_cyclecount.c | 2 +- app/test-crypto-perf/cperf_test_throughput.c | 4 +- app/test-crypto-perf/cperf_test_verify.c | 2 +- doc/guides/tools/cryptoperf.rst | 142 ++++++++ usertools/configs/crypto-perf-aesni-gcm.json | 99 ++++++ usertools/configs/crypto-perf-aesni-mb.json | 108 ++++++ usertools/configs/crypto-perf-qat.json | 94 ++++++ usertools/dpdk-graph-crypto-perf.py | 309 ++++++++++++++++++ 10 files changed, 761 insertions(+), 6 deletions(-) create mode 100644 usertools/configs/crypto-perf-aesni-gcm.json create mode 100644 usertools/configs/crypto-perf-aesni-mb.json create mode 100644 usertools/configs/crypto-perf-qat.json create mode 100755 usertools/dpdk-graph-crypto-perf.py
Comments
On 14/01/2021 10:41 AM, Ciara Power wrote: > This patchset introduces a python script to run various crypto performance > test cases, and graph the results in a consumable manner. The test suites > are configured via JSON file. Some config files are provided, > or the user may create one. Currently throughput and latency ptests for > devices crypto_qat, crypto_aesni_mb and crypto_aesni_gcm are supported. > > The final collection of graphs are output in PDF format, with multiple PDFs > per test suite, one for each graph type. > > Some fixes are included for the throughput performance test and latency > performance test csv outputs also. > > v2: > - Reduced changes to only fix csv format for all perf test types. > - Added functionality for additional args such as config file, > output directory and verbose. > - Improved help text for script. > - Improved script console output. > - Added support for latency test cases with burst or buffer size lists. > - Split config file into smaller config files, one for each device. > - Split output PDFs into smaller files, based on test suite graph types. > - Modified output directory naming and structure. > - Made some general improvements to script. > - Updated and improved documentation. > > Ciara Power (4): > test/cryptodev: fix latency test csv output > test/cryptodev: fix csv output format > usertools: add script to graph crypto perf results > maintainers: update crypto perf app maintainers > > MAINTAINERS | 3 + > app/test-crypto-perf/cperf_test_latency.c | 4 +- > .../cperf_test_pmd_cyclecount.c | 2 +- > app/test-crypto-perf/cperf_test_throughput.c | 4 +- > app/test-crypto-perf/cperf_test_verify.c | 2 +- > doc/guides/tools/cryptoperf.rst | 142 ++++++++ > usertools/configs/crypto-perf-aesni-gcm.json | 99 ++++++ > usertools/configs/crypto-perf-aesni-mb.json | 108 ++++++ > usertools/configs/crypto-perf-qat.json | 94 ++++++ > usertools/dpdk-graph-crypto-perf.py | 309 ++++++++++++++++++ > 10 files changed, 761 insertions(+), 6 deletions(-) > create mode 100644 usertools/configs/crypto-perf-aesni-gcm.json > create mode 100644 usertools/configs/crypto-perf-aesni-mb.json > create mode 100644 usertools/configs/crypto-perf-qat.json > create mode 100755 usertools/dpdk-graph-crypto-perf.py > Series Acked-by: Declan Doherty <declan.doherty@intel.com>
> On 14/01/2021 10:41 AM, Ciara Power wrote: > > This patchset introduces a python script to run various crypto performance > > test cases, and graph the results in a consumable manner. The test suites > > are configured via JSON file. Some config files are provided, > > or the user may create one. Currently throughput and latency ptests for > > devices crypto_qat, crypto_aesni_mb and crypto_aesni_gcm are supported. > > > > The final collection of graphs are output in PDF format, with multiple PDFs > > per test suite, one for each graph type. > > > > Some fixes are included for the throughput performance test and latency > > performance test csv outputs also. > > > > v2: > > - Reduced changes to only fix csv format for all perf test types. > > - Added functionality for additional args such as config file, > > output directory and verbose. > > - Improved help text for script. > > - Improved script console output. > > - Added support for latency test cases with burst or buffer size lists. > > - Split config file into smaller config files, one for each device. > > - Split output PDFs into smaller files, based on test suite graph types. > > - Modified output directory naming and structure. > > - Made some general improvements to script. > > - Updated and improved documentation. > > > > Ciara Power (4): > > test/cryptodev: fix latency test csv output > > test/cryptodev: fix csv output format > > usertools: add script to graph crypto perf results > > maintainers: update crypto perf app maintainers > > > > MAINTAINERS | 3 + > > app/test-crypto-perf/cperf_test_latency.c | 4 +- > > .../cperf_test_pmd_cyclecount.c | 2 +- > > app/test-crypto-perf/cperf_test_throughput.c | 4 +- > > app/test-crypto-perf/cperf_test_verify.c | 2 +- > > doc/guides/tools/cryptoperf.rst | 142 ++++++++ > > usertools/configs/crypto-perf-aesni-gcm.json | 99 ++++++ > > usertools/configs/crypto-perf-aesni-mb.json | 108 ++++++ > > usertools/configs/crypto-perf-qat.json | 94 ++++++ > > usertools/dpdk-graph-crypto-perf.py | 309 ++++++++++++++++++ > > 10 files changed, 761 insertions(+), 6 deletions(-) > > create mode 100644 usertools/configs/crypto-perf-aesni-gcm.json > > create mode 100644 usertools/configs/crypto-perf-aesni-mb.json > > create mode 100644 usertools/configs/crypto-perf-qat.json > > create mode 100755 usertools/dpdk-graph-crypto-perf.py > > > > Series Acked-by: Declan Doherty <declan.doherty@intel.com> Applied to dpdk-next-crypto Thanks.
15/01/2021 16:54, Akhil Goyal: > > On 14/01/2021 10:41 AM, Ciara Power wrote: > > > Ciara Power (4): > > > test/cryptodev: fix latency test csv output > > > test/cryptodev: fix csv output format > > > usertools: add script to graph crypto perf results > > > maintainers: update crypto perf app maintainers > > > > > > MAINTAINERS | 3 + > > > app/test-crypto-perf/cperf_test_latency.c | 4 +- > > > .../cperf_test_pmd_cyclecount.c | 2 +- > > > app/test-crypto-perf/cperf_test_throughput.c | 4 +- > > > app/test-crypto-perf/cperf_test_verify.c | 2 +- > > > doc/guides/tools/cryptoperf.rst | 142 ++++++++ > > > usertools/configs/crypto-perf-aesni-gcm.json | 99 ++++++ > > > usertools/configs/crypto-perf-aesni-mb.json | 108 ++++++ > > > usertools/configs/crypto-perf-qat.json | 94 ++++++ > > > usertools/dpdk-graph-crypto-perf.py | 309 ++++++++++++++++++ > > > 10 files changed, 761 insertions(+), 6 deletions(-) > > > create mode 100644 usertools/configs/crypto-perf-aesni-gcm.json > > > create mode 100644 usertools/configs/crypto-perf-aesni-mb.json > > > create mode 100644 usertools/configs/crypto-perf-qat.json > > > create mode 100755 usertools/dpdk-graph-crypto-perf.py > > > > > > > Series Acked-by: Declan Doherty <declan.doherty@intel.com> > > Applied to dpdk-next-crypto Sorry I missed this series and I discover it when looking at the crypto tree. I see that the crypto perf script and configs are located in usertools. I think it should be with the app in app/test-crypto-perf/ The usertools directory is for tools used in production by end users. Please consider changing the directory for the -rc2. Thanks
> 15/01/2021 16:54, Akhil Goyal: > > > On 14/01/2021 10:41 AM, Ciara Power wrote: > > > > Ciara Power (4): > > > > test/cryptodev: fix latency test csv output > > > > test/cryptodev: fix csv output format > > > > usertools: add script to graph crypto perf results > > > > maintainers: update crypto perf app maintainers > > > > > > > > MAINTAINERS | 3 + > > > > app/test-crypto-perf/cperf_test_latency.c | 4 +- > > > > .../cperf_test_pmd_cyclecount.c | 2 +- > > > > app/test-crypto-perf/cperf_test_throughput.c | 4 +- > > > > app/test-crypto-perf/cperf_test_verify.c | 2 +- > > > > doc/guides/tools/cryptoperf.rst | 142 ++++++++ > > > > usertools/configs/crypto-perf-aesni-gcm.json | 99 ++++++ > > > > usertools/configs/crypto-perf-aesni-mb.json | 108 ++++++ > > > > usertools/configs/crypto-perf-qat.json | 94 ++++++ > > > > usertools/dpdk-graph-crypto-perf.py | 309 ++++++++++++++++++ > > > > 10 files changed, 761 insertions(+), 6 deletions(-) > > > > create mode 100644 usertools/configs/crypto-perf-aesni-gcm.json > > > > create mode 100644 usertools/configs/crypto-perf-aesni-mb.json > > > > create mode 100644 usertools/configs/crypto-perf-qat.json > > > > create mode 100755 usertools/dpdk-graph-crypto-perf.py > > > > > > > > > > Series Acked-by: Declan Doherty <declan.doherty@intel.com> > > > > Applied to dpdk-next-crypto > > Sorry I missed this series and I discover it when looking at the crypto tree. > I see that the crypto perf script and configs are located in usertools. > I think it should be with the app in app/test-crypto-perf/ > The usertools directory is for tools used in production by end users. > > Please consider changing the directory for the -rc2. > Thanks > Removed from next-crypto for now.