DPDK patches and discussions
 help / color / mirror / Atom feed
From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "Doherty, Declan" <declan.doherty@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] aesni_gcm: PMD to support AES_GCM crypto	operations
Date: Sat, 30 Jan 2016 16:40:53 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA674AEF01@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1454159388-6267-1-git-send-email-declan.doherty@intel.com>


> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Declan Doherty
> Sent: Saturday, January 30, 2016 1:10 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] aesni_gcm: PMD to support AES_GCM crypto
> operations
> 
> This patch provides the implementation of an AES-NI accelerated crypto
> PMD
> which is dependent on Intel's multi-buffer library, see the white paper
> "Fast Multi-buffer IPsec Implementations on Intel®  Architecture
> Processors"
> 
> This PMD supports AES_GCM authenticated encryption and authenticated
> decryption using
> 128-bit AES keys
> 
> The patch also contains the related unit tests functions for the
> implemented functionality
> 
> Signed-off-by: Declan Doherty <declan.doherty@intel.com>
> ---
>  MAINTAINERS                                        |   4 +
>  app/test/test_cryptodev.c                          | 462
> +++++++++++++++++++
>  app/test/test_cryptodev_gcm_test_vectors.h         | 423
> +++++++++++++++++
>  config/common_linuxapp                             |  11 +-
>  config/defconfig_i686-native-linuxapp-gcc          |  10 +
>  drivers/crypto/Makefile                            |   1 +
>  drivers/crypto/aesni_gcm/Makefile                  |  66 +++
>  drivers/crypto/aesni_gcm/aesni_gcm_ops.h           | 127 ++++++
>  drivers/crypto/aesni_gcm/aesni_gcm_pmd.c           | 498
> +++++++++++++++++++++
>  drivers/crypto/aesni_gcm/aesni_gcm_pmd_ops.c       | 292 ++++++++++++
>  drivers/crypto/aesni_gcm/aesni_gcm_pmd_private.h   | 120 +++++
>  .../crypto/aesni_gcm/rte_pmd_aesni_gcm_version.map |   3 +
>  lib/librte_cryptodev/rte_cryptodev.h               |   5 +
>  mk/rte.app.mk                                      |  11 +-
>  14 files changed, 2028 insertions(+), 5 deletions(-)
>  create mode 100644 app/test/test_cryptodev_gcm_test_vectors.h
>  create mode 100644 drivers/crypto/aesni_gcm/Makefile
>  create mode 100644 drivers/crypto/aesni_gcm/aesni_gcm_ops.h
>  create mode 100644 drivers/crypto/aesni_gcm/aesni_gcm_pmd.c
>  create mode 100644 drivers/crypto/aesni_gcm/aesni_gcm_pmd_ops.c
>  create mode 100644 drivers/crypto/aesni_gcm/aesni_gcm_pmd_private.h
>  create mode 100644
> drivers/crypto/aesni_gcm/rte_pmd_aesni_gcm_version.map
> 

There should be an update to the Crypto Device Drivers guide for the new PMD.


Tim

  reply	other threads:[~2016-01-30 16:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-30 13:09 Declan Doherty
2016-01-30 16:40 ` O'Driscoll, Tim [this message]
2016-03-08 10:09 ` [dpdk-dev] [PATCH v2] " Pablo de Lara
2016-03-08 11:22   ` De Lara Guarch, Pablo
2016-03-08 11:26   ` [dpdk-dev] [PATCH v3] " Pablo de Lara
2016-03-10 16:41     ` [dpdk-dev] [PATCH v4] " Pablo de Lara
2016-03-10 18:53       ` John Griffin
2016-03-10 23:45         ` Thomas Monjalon
2016-03-10 23:34       ` Thomas Monjalon

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=26FA93C7ED1EAA44AB77D62FBE1D27BA674AEF01@IRSMSX108.ger.corp.intel.com \
    --to=tim.odriscoll@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    /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).