DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	"Griffin, John" <john.griffin@intel.com>
Subject: Re: [dpdk-dev] [PATCH] test: adding AES cipher-only tests on QAT PMD
Date: Fri, 25 Nov 2016 14:13:52 +0000	[thread overview]
Message-ID: <80307F746F1522479831AB1253B7024E70C403@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <1480012164-17395-1-git-send-email-fiona.trahe@intel.com>



> -----Original Message-----
> From: Trahe, Fiona
> Sent: Thursday, November 24, 2016 6:29 PM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Trahe, Fiona
> <fiona.trahe@intel.com>; Griffin, John <john.griffin@intel.com>; Kusztal,
> ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH] test: adding AES cipher-only tests on QAT PMD
> 
> Extended functional AES-CBC and AES-CTR cipher-only tests to run on QAT
> PMD.
> Added AES_CBC cipher-only performance tests on QAT PMD.
> No driver changes, but as now tested, QAT documentation is updated to
> remove constraint.
> 
> Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
> ---
>  app/test/test_cryptodev.c                  | 18 ++++++
>  app/test/test_cryptodev_aes_test_vectors.h | 36 +++++++----
>  app/test/test_cryptodev_perf.c             | 96 +++++++++++++++++++----------
> -
>  doc/guides/cryptodevs/qat.rst              |  1 -
>  4 files changed, 102 insertions(+), 49 deletions(-)
> 
> --
> 2.5.0
Acked-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>

  reply	other threads:[~2016-11-25 14:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24 18:29 Fiona Trahe
2016-11-25 14:13 ` Kusztal, ArkadiuszX [this message]
2016-11-30 15:16   ` De Lara Guarch, Pablo
     [not found]     ` <9DEEADBC57E43F4DA73B571777FECECA3C7CC7F7@SHSMSX103.ccr.corp.intel.com>
2016-12-13  8:09       ` Yang, GangX

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=80307F746F1522479831AB1253B7024E70C403@IRSMSX102.ger.corp.intel.com \
    --to=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).