DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Doherty, Declan" <declan.doherty@intel.com>,
	"Trahe, Fiona" <fiona.trahe@intel.com>,
	"Jain, Deepak K" <deepak.k.jain@intel.com>,
	"Griffin, John" <john.griffin@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/9] Add support for AES-CCM
Date: Mon, 9 Oct 2017 10:10:25 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CC2DE81@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20170921131123.16513-1-pablo.de.lara.guarch@intel.com>



> -----Original Message-----
> From: De Lara Guarch, Pablo
> Sent: Thursday, September 21, 2017 2:11 PM
> To: Doherty, Declan <declan.doherty@intel.com>; Trahe, Fiona
> <fiona.trahe@intel.com>; Jain, Deepak K <deepak.k.jain@intel.com>;
> Griffin, John <john.griffin@intel.com>
> Cc: dev@dpdk.org; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>
> Subject: [PATCH v2 0/9] Add support for AES-CCM
> 
> AES-CCM support is added in the OpenSSL and QAT PMDs.
> The PMDs and the test code have been reworked, to avoid duplications with
> AES-GCM code, as both algorithms are quite similar (both are AEAD
> algorithms).
> 
> Also, an optimization for AES-GCM (and AES-CCM after the last patch) has
> been introduced, initializing the OpenSSL Context with the key, at session
> creation, instead of for each operation.
> 
> Changes in v2:
> - Clarified API for AES-CCM
> - Modified OpenSSL PMD and sample apps to comply with API
> - Added support for AES-CCM in QAT
> - Extended test cases for 192 and 256 bit keys
> 
> Arek Kusztal (1):
>   crypto/qat: add AES-CCM support
> 
> Pablo de Lara (8):
>   cryptodev: clarify API for AES-CCM
>   examples/l2fwd-crypto: add AES-CCM support
>   app/crypto-perf: add AES-CCM support
>   crypto/openssl: fix AEAD parameters
>   crypto/openssl: init GCM key at session creation
>   crypto/openssl: add AES-CCM support
>   test/crypto: rename GCM test code
>   test/crypto: add AES-CCM tests
> 
>  app/test-crypto-perf/cperf_ops.c                   |  21 +-
>  app/test-crypto-perf/cperf_test_latency.c          |  34 +-
>  app/test-crypto-perf/cperf_test_throughput.c       |  34 +-
>  app/test-crypto-perf/cperf_test_verify.c           |  35 +-
>  doc/guides/cryptodevs/features/default.ini         |   3 +
>  doc/guides/cryptodevs/features/openssl.ini         |   3 +
>  doc/guides/cryptodevs/openssl.rst                  |   1 +
>  doc/guides/rel_notes/release_17_11.rst             |   6 +
>  drivers/crypto/openssl/rte_openssl_pmd.c           | 375 +++++++++++----
>  drivers/crypto/openssl/rte_openssl_pmd_ops.c       |  30 ++
>  drivers/crypto/qat/qat_adf/icp_qat_hw.h            |  20 +
>  drivers/crypto/qat/qat_adf/qat_algs_build_desc.c   |  28 ++
>  drivers/crypto/qat/qat_crypto.c                    | 169 ++++++-
>  drivers/crypto/qat/qat_crypto_capabilities.h       |  30 ++
>  examples/l2fwd-crypto/main.c                       |  44 +-
>  lib/librte_cryptodev/rte_crypto_sym.h              |  34 +-
>  test/test/test_cryptodev.c                         | 535 +++++++++++++++------
>  ...ectors.h => test_cryptodev_aead_test_vectors.h} | 516
> ++++++++++++++++++--
>  test/test/test_cryptodev_perf.c                    |   2 +-
>  19 files changed, 1570 insertions(+), 350 deletions(-)  rename
> test/test/{test_cryptodev_gcm_test_vectors.h =>
> test_cryptodev_aead_test_vectors.h} (92%)
> 
> --
> 2.9.4

Applied to dpdk-next-crypto.
Thanks,

Pablo

      parent reply	other threads:[~2017-10-09 10:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-18  8:07 [dpdk-dev] [PATCH 0/4] " Pablo de Lara
2017-08-18  8:07 ` [dpdk-dev] [PATCH 1/4] crypto/openssl: fix AEAD parameters Pablo de Lara
2017-08-18  8:07 ` [dpdk-dev] [PATCH] test/crypto: rename GCM test code Pablo de Lara
2017-08-18 16:09   ` De Lara Guarch, Pablo
2017-08-18  8:07 ` [dpdk-dev] [PATCH 2/4] crypto/openssl: init GCM key at session creation Pablo de Lara
2017-08-18  8:07 ` [dpdk-dev] [PATCH 3/4] test/crypto: rename GCM test code Pablo de Lara
2017-08-18  8:07 ` [dpdk-dev] [PATCH 4/4] crypto/openssl: add AES-CCM support Pablo de Lara
2017-09-21 13:11 ` [dpdk-dev] [PATCH v2 0/9] Add support for AES-CCM Pablo de Lara
2017-09-21 13:11   ` [dpdk-dev] [PATCH v2 1/9] cryptodev: clarify API " Pablo de Lara
2017-10-09  9:57     ` Trahe, Fiona
2017-09-21 13:11   ` [dpdk-dev] [PATCH v2 2/9] examples/l2fwd-crypto: add AES-CCM support Pablo de Lara
2017-09-21 13:11   ` [dpdk-dev] [PATCH v2 3/9] app/crypto-perf: " Pablo de Lara
2017-09-21 13:11   ` [dpdk-dev] [PATCH v2 4/9] crypto/openssl: fix AEAD parameters Pablo de Lara
2017-09-21 13:11   ` [dpdk-dev] [PATCH v2 5/9] crypto/openssl: init GCM key at session creation Pablo de Lara
2017-09-21 13:11   ` [dpdk-dev] [PATCH v2 6/9] crypto/openssl: add AES-CCM support Pablo de Lara
2017-09-21 13:11   ` [dpdk-dev] [PATCH v2 7/9] crypto/qat: " Pablo de Lara
2017-10-09  9:55     ` Trahe, Fiona
2017-09-21 13:11   ` [dpdk-dev] [PATCH v2 8/9] test/crypto: rename GCM test code Pablo de Lara
2017-09-21 13:11   ` [dpdk-dev] [PATCH v2 9/9] test/crypto: add AES-CCM tests Pablo de Lara
2017-10-05  9:12   ` [dpdk-dev] [PATCH v2 0/9] Add support for AES-CCM Zhang, Roy Fan
2017-10-09 10:10   ` De Lara Guarch, Pablo [this message]

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=E115CCD9D858EF4F90C690B0DCB4D8976CC2DE81@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=deepak.k.jain@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=john.griffin@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).