From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 93370A0A05; Tue, 19 Jan 2021 18:31:09 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 508B8140F2B; Tue, 19 Jan 2021 18:31:09 +0100 (CET) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id D50A0140F2A for ; Tue, 19 Jan 2021 18:31:07 +0100 (CET) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 6C54F5C0063; Tue, 19 Jan 2021 12:31:07 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Tue, 19 Jan 2021 12:31:07 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm3; bh= bI28iWpYhWiCbC7YNsN0uGaBdfIrxjBl55NUOB8eFHU=; b=l4N0h0WOSixNYD9E B3bxJJZjDolAKP1/VzZiQMlfuahMiTqxqFzyuksHz7e7DBXp0XTJSyvcGfPmeTRv MdyrW6rHN9jvbHcsTiaH9E8tX25MxGbqbFQwBf813eLkDW3bZSd/0UK347+SijFQ Im+Jtn2N6ttCPvdx1MHF/5oFBLeeldp9QOmu/I4cPsV2rATN4udZz9fjmYTU77AF v2XGnE3+Zr/AIE1SHStE4AAOm30oJ+BIT+ZWrn1d/qxTlLFWeIzTM6uvO8KwyLSi zETSpLU6aHebXDCc7DMM3DTbMwu9dWXJvFJrxlqvWvuHe2g3+HqmjmoBnaGfzxup PYN/Pg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=bI28iWpYhWiCbC7YNsN0uGaBdfIrxjBl55NUOB8eF HU=; b=ffvik2l+OcZW9MvYrNKOTTK7AILKFuGsfBzREI9tyxxHvTMitQCV8BeOV TRtzUDLiBc1RXEdm9qPCB8lJhBXxdltjbTTc1dTmSo5kt95RWiu8r28xUalCgzyA EDVF/jBV/SZan3XLaGoG89175hK28/cnPAIkmmPSA/PCTa90nbgaW48WPitK4gSP 2RWX67BlHLmF8piJK9Ht0vihOFr8bJciBUoWd+f8ppEBwiWQLd2i7SnkHw/b3T3R UToScBsRC2/ywLTGIgC2miBTlnisyXY6HWS/JR8Wi4Hgc3JHxdkPiyIj0aDKcZPe Pb7X0W0ujikS7tg7jj1RyIagVriMQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledruddtgddutdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepudeggfdvfeduffdtfeeglefghfeukefgfffhueejtdetuedtjeeu ieeivdffgeehnecukfhppeejjedrudefgedrvddtfedrudekgeenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghl ohhnrdhnvght X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id CBAAA24005D; Tue, 19 Jan 2021 12:31:05 -0500 (EST) From: Thomas Monjalon To: Ciara Power , Akhil Goyal Cc: "Doherty, Declan" , "dev@dpdk.org" , "stephen@networkplumber.org" , "adamx.dybkowski@intel.com" Date: Tue, 19 Jan 2021 18:31:04 +0100 Message-ID: <12731324.V2GDU5VsPC@thomas> In-Reply-To: References: <20201211173114.1924772-1-ciara.power@intel.com> <1578842a-f980-73e0-a3ce-a40b5e29c418@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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 > > 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