DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Jain, Deepak K" <deepak.k.jain@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	"Griffin, John" <john.griffin@intel.com>
Subject: Re: [dpdk-dev] [PATCH] app/test: add crypto continual tests
Date: Fri, 14 Oct 2016 08:18:19 +0000	[thread overview]
Message-ID: <A09C9DDE180C7E429EC68E2BFB95C903394766D2@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <1476361061-7366-1-git-send-email-arkadiuszx.kusztal@intel.com>



> -----Original Message-----
> From: Kusztal, ArkadiuszX
> Sent: Thursday, October 13, 2016 1:18 PM
> To: dev@dpdk.org
> Cc: Trahe, Fiona <fiona.trahe@intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>; Griffin, John <john.griffin@intel.com>;
> Jain, Deepak K <deepak.k.jain@intel.com>; Kusztal, ArkadiuszX
> <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH] app/test: add crypto continual tests
> 
> This commit adds continual performace tests to Intel(R) QuickAssist
> Technology tests suite. Performance tests are run continually with some
> number of repeating loops.
> 
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> ---
>  app/test/test_cryptodev_perf.c | 133
> ++++++++++++++++++++++++++++++++++++-----
>  1 file changed, 119 insertions(+), 14 deletions(-)
> 
> diff --git a/app/test/test_cryptodev_perf.c
> b/app/test/test_cryptodev_perf.c index 43a7166..dd741fa 100644
> --- a/app/test/test_cryptodev_perf.c
> --
> 2.1.0
Acked-by: Deepak Kumar Jain <deepak.k.jain@intel.com>

  reply	other threads:[~2016-10-14  8:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-13 12:17 Arek Kusztal
2016-10-14  8:18 ` Jain, Deepak K [this message]
2016-10-17 18:35 ` 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=A09C9DDE180C7E429EC68E2BFB95C903394766D2@IRSMSX107.ger.corp.intel.com \
    --to=deepak.k.jain@intel.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).