From: "Jain, Deepak K" <deepak.k.jain@intel.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] [PATCH 2/4] test: add AES DOCSIS tests for QAT PMD
Date: Fri, 3 Mar 2017 11:45:41 +0000 [thread overview]
Message-ID: <A09C9DDE180C7E429EC68E2BFB95C90339548F96@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <1488459792-30066-3-git-send-email-fiona.trahe@intel.com>
> -----Original Message-----
> From: Trahe, Fiona
> Sent: Thursday, March 2, 2017 1:03 PM
> To: dev@dpdk.org; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Cc: Jain, Deepak K <deepak.k.jain@intel.com>; Trahe, Fiona
> <fiona.trahe@intel.com>
> Subject: [PATCH 2/4] test: add AES DOCSIS tests for QAT PMD
>
> Extend test suite to run AES DOCSIS tests on Intel QuickAssist PMD.
>
> Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
> ---
> app/test/test_cryptodev.c | 18 ++++++++++++++++++
> app/test/test_cryptodev_aes_test_vectors.h | 18 ++++++++++++------
> 2 files changed, 30 insertions(+), 6 deletions(-)
>
> --
> 2.5.0
Acked-by: Deepak Kumar Jain <deepak.k.jain@intel.com>
next prev parent reply other threads:[~2017-03-03 11:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 13:03 [dpdk-dev] [PATCH 0/4] crypto/qat: add DOCSISBPI mode support Fiona Trahe
2017-03-02 13:03 ` [dpdk-dev] [PATCH 1/4] crypto/qat: adding docsisbpi " Fiona Trahe
2017-03-03 11:44 ` Jain, Deepak K
2017-03-02 13:03 ` [dpdk-dev] [PATCH 2/4] test: add AES DOCSIS tests for QAT PMD Fiona Trahe
2017-03-03 11:45 ` Jain, Deepak K [this message]
2017-03-06 5:35 ` Yang, GangX
2017-03-02 13:03 ` [dpdk-dev] [PATCH 3/4] test: add DES " Fiona Trahe
2017-03-03 11:51 ` Jain, Deepak K
2017-03-06 6:21 ` Yang, GangX
2017-03-02 13:03 ` [dpdk-dev] [PATCH 4/4] test: added crypto OOP tests Fiona Trahe
2017-03-03 11:45 ` Jain, Deepak K
2017-03-30 18:38 ` [dpdk-dev] [PATCH 0/4] crypto/qat: add DOCSISBPI mode support 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=A09C9DDE180C7E429EC68E2BFB95C90339548F96@IRSMSX107.ger.corp.intel.com \
--to=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@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).