From: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/3] crypto/aesni_mb: add aes-gcm support
Date: Wed, 10 Oct 2018 09:49:14 +0000 [thread overview]
Message-ID: <06EE24DD0B19E248B53F6DC8657831559E7F1B@HASMSX110.ger.corp.intel.com> (raw)
In-Reply-To: <20181009201056.37344-1-roy.fan.zhang@intel.com>
> -----Original Message-----
> From: Zhang, Roy Fan
> Sent: Tuesday, October 9, 2018 10:11 PM
> To: dev@dpdk.org
> Cc: akhil.goyal@nxp.com; Kusztal, ArkadiuszX
> <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH v2 0/3] crypto/aesni_mb: add aes-gcm support
>
> This patchset adds the AES-GCM algorithm support to AESNI-MB Cryptodev
> PMD and updates the unit test and documentations along.
>
> v2:
> - rebased on top of latest dpdk-next-crypto.
> - removed incorrect __rte_unused macros.
>
> Fan Zhang (3):
> crypto/aesni_mb: add aes-gcm algorithm support
> test/test_cryptodev: add AES-GCM tests to AESNI-MB
> doc: update cryptodev and release note
>
> doc/guides/cryptodevs/aesni_mb.rst | 1 +
> doc/guides/rel_notes/release_18_11.rst | 4 +
> drivers/crypto/aesni_mb/aesni_mb_ops.h | 28 +++-
> drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c | 160
> +++++++++++++++------
> drivers/crypto/aesni_mb/rte_aesni_mb_pmd_ops.c | 30 ++++
> drivers/crypto/aesni_mb/rte_aesni_mb_pmd_private.h | 3 +
> test/test/test_cryptodev.c | 114 +++++++++++++++
> 7 files changed, 293 insertions(+), 47 deletions(-)
>
> --
> 2.13.6
Series-acked-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
next prev parent reply other threads:[~2018-10-10 9:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 10:44 [dpdk-dev] [PATCH " Fan Zhang
2018-09-07 10:44 ` [dpdk-dev] [PATCH 1/3] crypto/aesni_mb: add aes-gcm algorithm support Fan Zhang
2018-09-07 10:44 ` [dpdk-dev] [PATCH 2/3] test/test_cryptodev: add AES-GCM tests to AESNI-MB Fan Zhang
2018-09-07 10:44 ` [dpdk-dev] [PATCH 3/3] doc: update cryptodev and release note Fan Zhang
2018-10-09 20:10 ` [dpdk-dev] [PATCH v2 0/3] crypto/aesni_mb: add aes-gcm support Fan Zhang
2018-10-09 20:10 ` [dpdk-dev] [PATCH v2 1/3] crypto/aesni_mb: add aes-gcm algorithm support Fan Zhang
2018-10-09 20:10 ` [dpdk-dev] [PATCH v2 2/3] test/test_cryptodev: add AES-GCM tests to AESNI-MB Fan Zhang
2018-10-09 20:10 ` [dpdk-dev] [PATCH v2 3/3] doc: update cryptodev and release note Fan Zhang
2018-10-10 9:49 ` Kusztal, ArkadiuszX [this message]
2018-10-10 10:42 ` [dpdk-dev] [PATCH v2 0/3] crypto/aesni_mb: add aes-gcm support Akhil Goyal
2018-10-10 11:04 ` [dpdk-dev] [PATCH v3 " Fan Zhang
2018-10-10 11:04 ` [dpdk-dev] [PATCH v3 1/3] crypto/aesni_mb: add aes-gcm algorithm support Fan Zhang
2018-10-10 11:04 ` [dpdk-dev] [PATCH v3 2/3] test/test_cryptodev: add AES-GCM tests to AESNI-MB Fan Zhang
2018-10-10 11:04 ` [dpdk-dev] [PATCH v3 3/3] doc: update cryptodev and release note Fan Zhang
2018-10-10 11:39 ` [dpdk-dev] [PATCH v3 0/3] crypto/aesni_mb: add aes-gcm support Akhil Goyal
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=06EE24DD0B19E248B53F6DC8657831559E7F1B@HASMSX110.ger.corp.intel.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=roy.fan.zhang@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).