From: Akhil Goyal <akhil.goyal@nxp.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>,
<declan.doherty@intel.com>, <hemant.agrawal@nxp.com>,
<jerin.jacob@caviumnetworks.com>, <fiona.trahe@intel.com>,
<deepak.k.jain@intel.com>, <john.griffin@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v2] test/crypto: remove crypto perf tests
Date: Thu, 5 Oct 2017 18:32:14 +0530 [thread overview]
Message-ID: <7c5e18e9-44b3-8dbe-eeac-d59404aa70e5@nxp.com> (raw)
In-Reply-To: <20171004064838.29827-1-pablo.de.lara.guarch@intel.com>
On 10/4/2017 12:18 PM, Pablo de Lara wrote:
> Since the crypto perf application is flexible enough
> to cover all the crypto performance tests, these are not needed
> anymore, so they will be removed to avoid duplications.
> Besides, the crypto perf application gives the user more options
> to get performance, for every single supported algorithm,
> such as varying the buffer size as the user wants.
>
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> ---
>
> Changes in v2:
> - Rebased against latest code
> - Added note in release notes
>
> doc/guides/rel_notes/release_17_11.rst | 15 +
> test/test/Makefile | 1 -
> test/test/test_cryptodev_perf.c | 4932 --------------------------------
> 3 files changed, 15 insertions(+), 4933 deletions(-)
> delete mode 100644 test/test/test_cryptodev_perf.c
>
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
next prev parent reply other threads:[~2017-10-05 13:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 19:57 [PATCH] test/crypto: remove crypto perf tests Pablo de Lara
2017-07-08 17:03 ` Thomas Monjalon
2017-07-11 10:54 ` De Lara Guarch, Pablo
2017-10-04 6:48 ` [PATCH v2] " Pablo de Lara
2017-10-05 9:34 ` Zhang, Roy Fan
2017-10-05 13:02 ` Akhil Goyal [this message]
2017-10-05 13:34 ` De Lara Guarch, Pablo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7c5e18e9-44b3-8dbe-eeac-d59404aa70e5@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=declan.doherty@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=john.griffin@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.